![\"\"](\"https://www.googleapis.com/download/storage/v1/b/kaggle-forum-message-attachments/o/inbox%2F2262906%2F1d3b190f07a6980d9d412971b79d7a66%2FScreenshot%202025-02-21%20153020.png?generation=1740177617045790&alt=media\")
In dataset description is says that every video is 30fps.
\nWhen using cv2 to read out the properties of each mp4, I get many videos that says it has a different FPS than 30. Is it 30 or should I use the one in video? This is ofcourse crucial to get where in the video the alert/event is.
\n
Hey! You are right, our videos are approximately 30 FPS but there is some variability. Please take the video metadata into consideration. Thank you for bringing this up!
", "rawMarkdown": "Hey! You are right, our videos are **approximately** 30 FPS but there is some variability. Please take the video metadata into consideration. Thank you for bringing this up! \n", "votes": 1 }, { "id": 3131786, "postDate": "2025-02-23T09:49:06.857Z", "content": "The data for the competition is also posted on https://huggingface.co/datasets/nexar-ai/nexar_collision_prediction , where it is noted that every video is 30 fps.
", "rawMarkdown": "The data for the competition is also posted on https://huggingface.co/datasets/nexar-ai/nexar_collision_prediction , where it is noted that every video is 30 fps.", "votes": 1, "replies": [ { "id": 3132261, "postDate": "2025-02-24T02:03:01.120Z", "content": "But it is not, according to metadata. And it is CRUCIAL to know if the Alert and Event labels (that are in seconds from video start) are correct, so we can get the correct video frame numbers for those. I am using the metadata, but think that some are a bit off when inspecting where my model goes wrong. @danielcmoura
", "rawMarkdown": "But it is not, according to metadata. And it is CRUCIAL to know if the Alert and Event labels (that are in seconds from video start) are correct, so we can get the correct video frame numbers for those. I am using the metadata, but think that some are a bit off when inspecting where my model goes wrong. @danielcmoura " } ] }, { "id": 3130677, "postDate": "2025-02-21T22:37:44.583Z", "content": "In dataset description is says that every video is 30fps.
\nWhen using cv2 to read out the properties of each mp4, I get many videos that says it has a different FPS than 30. Is it 30 or should I use the one in video? This is ofcourse crucial to get where in the video the alert/event is.
\n
I used the actual fps read from cv2. But it would be nice to have the host clear this up.
", "rawMarkdown": "I used the actual fps read from cv2. But it would be nice to have the host clear this up.", "votes": 2 }, { "id": 3130967, "postDate": "2025-02-22T10:14:10.330Z", "content": "I would take the metadata. They're around 30 fps
", "rawMarkdown": "I would take the metadata. They're around 30 fps", "votes": 2, "replies": [ { "id": 3131351, "postDate": "2025-02-22T18:14:07.773Z", "content": "That's what I did, but I hope which frame / alert/event time are calculated based on the metadata framerate as well!
", "rawMarkdown": "That's what I did, but I hope which frame / alert/event time are calculated based on the metadata framerate as well!", "votes": 1 } ] }, { "id": 3131252, "postDate": "2025-02-22T16:21:26.810Z", "content": "Nice catch! I didn't even bother to check the real FPS.
", "rawMarkdown": "Nice catch! I didn't even bother to check the real FPS.", "votes": 1, "isDeleted": true } ], "comments": [ { "id": 3141185, "author_name": "Daniel Moura", "author_url": "", "post_date": "2025-03-05T09:53:54.330000", "content": "Hey! You are right, our videos are approximately 30 FPS but there is some variability. Please take the video metadata into consideration. Thank you for bringing this up!
", "votes": 1, "replies": [] }, { "id": 3131786, "author_name": "Diana1800", "author_url": "", "post_date": "2025-02-23T09:49:06.857000", "content": "The data for the competition is also posted on https://huggingface.co/datasets/nexar-ai/nexar_collision_prediction , where it is noted that every video is 30 fps.
", "votes": 1, "replies": [ { "id": 3132261, "author_name": "PaulEE", "author_url": "", "post_date": "2025-02-24T02:03:01.120000", "content": "But it is not, according to metadata. And it is CRUCIAL to know if the Alert and Event labels (that are in seconds from video start) are correct, so we can get the correct video frame numbers for those. I am using the metadata, but think that some are a bit off when inspecting where my model goes wrong. @danielcmoura
", "votes": 0, "replies": [] } ] }, { "id": 3131469, "author_name": "SLi", "author_url": "", "post_date": "2025-02-22T21:02:24.317000", "content": "I used the actual fps read from cv2. But it would be nice to have the host clear this up.
", "votes": 2, "replies": [] }, { "id": 3130967, "author_name": "Ángel Jacinto Sánchez Ruiz", "author_url": "", "post_date": "2025-02-22T10:14:10.330000", "content": "I would take the metadata. They're around 30 fps
", "votes": 2, "replies": [ { "id": 3131351, "author_name": "PaulEE", "author_url": "", "post_date": "2025-02-22T18:14:07.773000", "content": "That's what I did, but I hope which frame / alert/event time are calculated based on the metadata framerate as well!
", "votes": 1, "replies": [] } ] }, { "id": 3131252, "author_name": "", "author_url": "", "post_date": "2025-02-22T16:21:26.810000", "content": "Nice catch! I didn't even bother to check the real FPS.
", "votes": 1, "replies": [] } ], "raw_markdown_by_id": { "3141185": "Hey! You are right, our videos are **approximately** 30 FPS but there is some variability. Please take the video metadata into consideration. Thank you for bringing this up! \n", "3131786": "The data for the competition is also posted on https://huggingface.co/datasets/nexar-ai/nexar_collision_prediction , where it is noted that every video is 30 fps.", "3130677": "In dataset description is says that every video is 30fps.\n\nWhen using cv2 to read out the properties of each mp4, I get many videos that says it has a different FPS than 30. Is it 30 or should I use the one in video? This is ofcourse crucial to get where in the video the alert/event is. \n\n", "3131469": "I used the actual fps read from cv2. But it would be nice to have the host clear this up.", "3130967": "I would take the metadata. They're around 30 fps", "3131252": "Nice catch! I didn't even bother to check the real FPS." } }