Is your feature request related to a problem? Please describe.
The issue arises when you try to extract frames from a video that isn't added to your project but may or may not be in your project videos folder. The program doesn't provide a clear message for this instead claiming the video files are corrupted, which doesn't help the end user and just causes confusion.
Describe the solution you'd like
It's up to the DLC team which is why I did not open a PR, but:
- Simply prompt the user to add the file to the project (or offer to do it for them), OR
- Change the pathing method so that the file pathing is relative instead of absolute, OR
- Both relative and absolute pathing are allowed
The last two aren't entirely related, but would fix problems that arise from uploading a project and attempting to work on the same project on multiple machines, for example. The latter is probably the only one that would be accepted over 2 so it's not a breaking change. Regardless, the issue of the incorrect error message must be addressed.
Describe alternatives you've considered
See above.
Additional context
These are all from my observations on my machines (main dev. Windows 11 PC, separate MacBook Pro M3 Pro) using DLC 3.0.0rc10. Specifically how pathing differs on Windows machines versus Mac, but I would assume the same issue results from having different users or roots as well.
Related comments from users: #3156 (here)
Is your feature request related to a problem? Please describe.
The issue arises when you try to extract frames from a video that isn't added to your project but may or may not be in your project
videosfolder. The program doesn't provide a clear message for this instead claiming the video files are corrupted, which doesn't help the end user and just causes confusion.Describe the solution you'd like
It's up to the DLC team which is why I did not open a PR, but:
The last two aren't entirely related, but would fix problems that arise from uploading a project and attempting to work on the same project on multiple machines, for example. The latter is probably the only one that would be accepted over 2 so it's not a breaking change. Regardless, the issue of the incorrect error message must be addressed.
Describe alternatives you've considered
See above.
Additional context
These are all from my observations on my machines (main dev. Windows 11 PC, separate MacBook Pro M3 Pro) using DLC 3.0.0rc10. Specifically how pathing differs on Windows machines versus Mac, but I would assume the same issue results from having different users or roots as well.
Related comments from users: #3156 (here)