-
-
Notifications
You must be signed in to change notification settings - Fork 16k
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
Invalid SOS parameters for sequential JPEG #11880
Comments
@aliaminibagh hi, The error message "Invalid SOS parameters for sequential JPEG" typically occurs when there is an issue with the image file format or it is corrupted. Please make sure that your custom dataset images are in a supported format such as JPEG or PNG. Also, check if the images are not corrupted and can be opened with an image viewer. If the issue still persists, please provide more information such as the version of YOLOv5 you are using, the steps you followed to train the dataset, and any relevant logs or error messages you encountered. This will help us investigate further. Additionally, if you have any other questions or need further assistance, feel free to ask. Thanks! |
Thanks a lot @glenn-jocher |
Hi @aliaminibagh, The error message "Invalid SOS parameters for sequential JPEG" typically occurs when there is an issue with the image file format or it is corrupted. Please make sure that your custom dataset images are in a supported format such as JPEG or PNG. Also, check if the images are not corrupted and can be opened with an image viewer. If the issue still persists, please provide more information such as the version of YOLOv5 you are using, the steps you followed to train the dataset, and any relevant logs or error messages you encountered. This will help us investigate further. Additionally, if you have any other questions or need further assistance, feel free to ask. Thanks! Glenn Jocher |
Search before asking
Question
when use yolo in train custom dataset, I encounter these expressions during training. Can you tell me the reason?
Additional
No response
The text was updated successfully, but these errors were encountered: