-
Notifications
You must be signed in to change notification settings - Fork 9.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Forward video has tearing artifacts #33998
Comments
While not yet reported yet, a447729c1d15ff89 might have the same issue (patienc3 on Discord). They might come in with a report or data of their own. |
Same issue observed in the route https://connect.comma.ai/a447729c1d15ff89/0000001b--0585570655 |
Thanks for the great report! We made a bunch of relevant changes here recently (mostly ISP + tinygrad), but nothing that particularly points at the fcam.
|
Reproduced on an AR0231 device. Repro procedure is reboot and cycle ignition a few times.
Appears to be in the raw bayer stream. Output fence not working properly? It's plausible that never quite worked correctly, but processing three cams masked over it. Output fence wait times on a bad start:
Can't repro running camerad alone in a tight loop. And another pattern
|
Had the same issue on my trip tonight. Lower third of the forward camera has this issue. Route: 5130484aa8069bad/00000007--b9a36bd4fa |
Reverting until this is fixed #34020. |
I had this happen to me earlier this year. Have not noticed it since. https://connect.comma.ai/164080f7933651c4/2024-04-07--11-04-32 |
Describe the bug
The first drive's after a cold boot's forward video is fine. The next ONROAD's forward video is not. Might need the screen to go dark in-between drives. The wide video seems fine on all the drives. Third drive and up seemed to be fine in one of the cases.
this one's first boot's drive is fine: https://connect.comma.ai/fe18f736cb0d7813/00000404--83516f16c4
second boot: fe18f736cb0d7813/0000040b--78d26612d7/2
replicate-prediction-08npcdqtxdrgw0ck3zarcbkw38.mp4
replicate-prediction-e6ka7a91qsrgt0ck3zbapd3f5m.mp4
Context: Vehicle started from cold boot, had a bit of a drive, saw TPMS low tire pressure, went back to house to get tire pump, pumped all four tires, started second drive, saw errors.
Did not attempt to drive the rest of the route with openpilot engaged. It was ping-ponging like mad, which isn't unexpected for this issue.
first boot is fine: https://connect.comma.ai/fe18f736cb0d7813/0000040a--0dbe63a02e
second boot: fe18f736cb0d7813/00000405--2b441abe00/9
replicate-prediction-wka85genthrgt0ck3zbbarsdhr.mp4
replicate-prediction-bnq25cnhbsrgw0ck3zb984fvhc.mp4
third to fifth drive seems fine?:
https://connect.comma.ai/fe18f736cb0d7813/00000406--f82bf78ec4
https://connect.comma.ai/fe18f736cb0d7813/00000407--a56e0a2bec
https://connect.comma.ai/fe18f736cb0d7813/00000408--9eb4d4c06f
Context: Just went out, got something to eat, groceries. Did use openpilot for rest of drive though. It didn't seem to be badly affected like the route above.
Provide a route where the issue occurs
fe18f736cb0d7813/0000040b--78d26612d7/2 , fe18f736cb0d7813/00000405--2b441abe00/9
openpilot version
master-ci
Additional info
Discord links:
feedback: https://discord.com/channels/469524606043160576/1305837783490891826
openpilot-experience: https://discord.com/channels/469524606043160576/616456819027607567/1305838954825777162
The text was updated successfully, but these errors were encountered: