File Loading Problems Error Message - the file has no audio or video streams...(it does)

Report · Apr 08, 2017

Using Adobe Premiere Pro CC 2017.0.2 (11.0.2 (47) Build), I am getting the error message on one of my .mp4 files that the file has no audio or video streams. Other files shot with the same settings, using the same camera, on the same day work fine.

The problematic file loads in any other program, it is an H.265 file with a 100 mbps bitrate, shot using a DJI Phantom 4 quadcopter stored in .mp4 file format. shot at 3840x2160 29.97p

The other files shot on the same shoot are the same format, and they load fine.

The problem file is 5 mins and 16 secs long and 3.67GB in size, it will NOT load in media encoder or Premiere pro but can playback in windows media player and loads in Mercalli v4 SAL.

The next largest file I have from that day is 2.68 GB in size and 3mins 50 secs in length. Adobe Premiere Pro and Media encoder load that file without any errors.

Is there some file size limit or something? This is not the first file anomaly I've found with this version of Premiere Pro, .mp4 files from my GoPro Hero 4 and 5 cameras shot at 1280x720 240p no longer work anymore unless I first tell the software to interpret the footage at something other than 240 fps. I have to put in 29.97 or 59.94 in the interpret footage for each clip or the sound module will crash.

Older versions of Adobe Premiere Pro can load the 720/240p files fine without having to change the framerate in the interpret footage section for each clip.

-Roger Uzun

Report · Apr 10, 2017

Start with steps 2h and i.

Unofficial Premiere Pro Troubleshooting Guide

If that didn't resolve the issue, are you able to load the offending file into AME and convert it to something else, like Cineform or DNx?

Report · Apr 10, 2017

Taking the file to a different computer running Adobe CC 2017 exhibits the same problem. It's nothing to do with the drive or windows 10. Loading the file in any other app I have is fine, all other apps load it and play it fine.

The only app I have that can transcode at all other than Adobe is Mercalli SAL v4. It loads and exports the file fine, and I can load the AVCHD file that mercalli exports into adobe without error.

I need the original H265 encoded file to load correctly into Premiere Pro, not a transcoded version of that file.

Other H265 files encoded the same way on the same day with the same camera load into Adobe just fine, its only this one file that generates the no valid streams error. This is the largest of the files, maybe a file size limitation of Adobe and H265 or something like that.

Like I said, lately adobe has been MUCH worse a loading files than it has in the past. I have another issue with 720/240p files from GoPro Hero Cameras. They actually do load, but if you don't manually tell adobe to interpret the footage at some frame rate below 240, it will crash as soon as you try and scrub the video or use the video in any way.

Report · Apr 11, 2017

I need the original H265 encoded file to load correctly into Premiere Pro, not a transcoded version of that file.

Need? Or want? I'm at a lack trying to think of situations for the former.

What I mean is, I believe you might be artificially limiting yourself here. Do what works.

Report · Jun 10, 2018

Jim_Simon wrote
I need the original H265 encoded file to load correctly into Premiere Pro, not a transcoded version of that file.
Need? Or want? I'm at a lack trying to think of situations for the former.
What I mean is, I believe you might be artificially limiting yourself here. Do what works.

Typical pro-Adobe, defensive, Jim Simon answer.

Transcoding and thus degrading the file quality is unacceptable. This is a widely reported problem elsewhere in these forums and the solution takes a little more than pointing to the usual "try this first" blow-off.

Report · Jun 11, 2018

JIm's answer wasn't a blow-off. It was simply a common-sense workaround to get the work out the door.

Transcoding to a high-quality "digitial intermediate" codec is a long-accepted and heavily used process for editing, color grading, and fx work. Most colorists I know always have any long-GOP media t-coded and use that media to grade rather than working with long-GOP on a grading timeline. These are folks working for major national/international b-cast channels and shows.

So ... your comment about t-coding thus degrading file quality is an odd one. From GoPro's own manual, in talking about editing with the media produced from their own cameras, came the following:

Is it at times annoying to have to plan for the time for t-coding & proxy creation? Sure.

Would we all like to have the app work so well on any hardware with any media it wasn't needed or at least more than useful? Sure.

Does the work need to get out today? Or early tomorrow? Or even the end of the week? If so, you just do what gets the job done. And plan for the time needed.

I had someone argue that PrPro's use of proxies was stupid, they should just have something like Resolve's "optimize media" option, because that of course just uses the original media, just that Resolve is smarter than PrPro so it can without making proxies.

Right.

"Optimized media" is Resolve's internal terminology for creating proxies for use instead of original media. Just like PrPro. It's in that long and luscious manual they put out for the app ... which in itself is a thing of beauty.

Neil

Report · Jun 11, 2018

Transcoding and thus degrading the file quality is unacceptable.

I don't believe Cineform or DNx will degrade it.