look at the property panel : it’s the wrong panel: we see the “video” properties. it should be the “photo / picture” properties (and it’s now impossible to check the “image sequence” because it is not shown!)
(note : if i open an old project created with a previous version, i can get the right property panel when i select an image sequence in the timeline.)
thank you for your answer. I did some more tests, with the old version.
I think the bug should be renamed “shotcut v23.05.x cannot open some JPG formats”
here are some screenshots.
if i import the JPG with the old version, the object is well created in the time line, and the new version sees it as an “image object”, and can display the right properties BUT cannot show the picture!
my jpg file is quite big, 42Mpix, from my camera… but shotcut has always been able to read it since 2 years i use it!
It is regular jpg, no special codec. i’ll send you one .
if i take a small JPG from internet, shotcut reads it without problem.
When I load this image in, the thumbnail across the application doesn’t generate for the Playlisted image. While I was going back in versions to the one that worked, I knew I found the right version when that thumbnail generated.
Shotcut is assuming the Codex MJPG which is weird since these are only JPG’s straight from my camera. Modifying the Track to “None” doesn’t help, nor does modifying the codec.
I went back to 22.10.22 to get this functionality back for my needs. Note: I went back two versions that failed, skipped a few, then found that this version was working.
For additional testing, if you would like a copy of one of these large JPG’s for troubleshooting please let me know. Happy to contribute.
I am not denying the bug. Before you said “4K” which is 3840x2160 (or 4096 wide). Now, you show something much higher. It can be beneficial to downscale an image larger than 4K, and there are other special use cases for very high res too. But for many people, where the majority of the image can be used, a workaround us to reduce resolution. I do not know exactly where the resolution fails, but I have one open now at 5568x4872 that is opening as a proper image. So, somewhere between that and yours.