Copy link to clipboard
Copied
PS 24.7 Windows 10.
Attempts to open or " Add Media" from certain MP4 files result in 'File cannot be opened' error.
Specific case: MP4 file from Android ( Pixel 6a) with current Android system and app updates is transfered is to this PC via Google Photos. These files open without error in Windows media player and other video apps ( incuding Blender). These same files do not open in PS and result in an error message.
File transfer from Android to PC via e-mail or dropbox results in same error.
If I transcode the same files to a new MP4, they open without error in PS.
All MP4 files not from this Android device open without error in this PS configuration.
This is reproducable with multiple video files from the same Android source source.
I suspect this is some kind of file header or other file attribute that is removed when I transcode the files?? Needless to say, transcodeing files back to same type is a major kink in the workflow.
I have attached a very brief video that exhibits this problem. This video opens on multiple apps on this PC, but results in error message in PS
Thanks for any assistance here.
Did you read my earlier reply?
I looked at your video in Premiere Pro and it is not the variable framerate that is the issue but the HEVC codec which is not readable in Photoshop. Either transcode as you were doing or record directly using H.264. I transcoded it to H.264 and kept the variable frame rate and it opened in Photoshop without issue.
Dave
Copy link to clipboard
Copied
MP4 is just a container. Your file is recorded with the HEVC codec which as far as I'm aware is not supported in Photoshop video even when the HEVC codecs are downloaded from Microsoft (Photoshop is an image editor with a few video functions added on).
To avoid transcoding, try setting your phone to record H264 which is probably what you are getting when you transcode
Dave
Copy link to clipboard
Copied
I also have this problem. In my case video from an android phone won't open in PS. In my case the message is soimply.... The Video file cannot be opened....
This file plays in the MS / WIndows 10 video player, and opens in other apps on the same PC. Dosen't seem to be a PC Driver issue, since multiple apps open it without issue. It is a larger file... ~ 1 gig. Any help is appreciated.
Copy link to clipboard
Copied
Does Photoshop give you any more information when you get the error?
Copy link to clipboard
Copied
In my case, the error message is not helpful being only, "Could not open diving video because the video file could not be opened"
It seems I will need to look at some format change when creating my videos on my Gopro 10.
Copy link to clipboard
Copied
Copy link to clipboard
Copied
I dug into this over the past few days. I'm not and expert... My diagnosis is:
I was trying to record video on Pixel 6a in higher defination. The Pixel 6a recorded at funky frame rates - one video was 47 FPS??
I figured this out by opening in Blender, the strip opened, but had funky audio errors. I fixed everything by resetting frame rates and audio rates, then all was OK. I'm suprised the windows video player handeled this file without hiccup?
It appears PS can't handle these wierd frame rates and just gives up. I don't have any of the Adobe specality video programs, I don't know if they would handle this beter. Blender is a bear to use, I had hoped PS would be an easier tool.
I'm going to dig into the phone setting to try to limit to standard resolutions, frame rate and Codec to see if this resolves the problem.
I've shot lots of video with my Nikon SLR, but it's really strict and limits formats to standard resolutions and frame rates - never ran into this problem from that source.
Copy link to clipboard
Copied
Did you read my earlier reply?
I looked at your video in Premiere Pro and it is not the variable framerate that is the issue but the HEVC codec which is not readable in Photoshop. Either transcode as you were doing or record directly using H.264. I transcoded it to H.264 and kept the variable frame rate and it opened in Photoshop without issue.
Dave
Copy link to clipboard
Copied
After even more time, this does indeed correct the issue. It's dissapointing both that the error code is so vauge, and that PS does not support what appears to be a not uncommon common and growing codec.