Re: Adobe Premiere Pro The File Has No Audio Or Video Streams
Eilal Pichardo
Now that I've gotten that out of the way, here's what's going on:
There seems to be something within certain .mov and .mp4 files that's not allowing this specific version of Premiere to import them. I say this because I have another, slightly older version of Premiere on my mac, and it imports the same files just fine. In fact, as a part of the project I'm working on, I had to use that to convert the videos to mp4s that the Premiere on Windows would like. I have also never, ever had this issue before, and I've been using Premiere for about 8 years, now. Keep in mind here, there are some other .mp4 and .mov files that I've been able to import without issue.
adobe premiere pro the file has no audio or video streams
Descargar archivo https://jfilte.com/2yPp92
I have been able to open the problematic files with Quicktime (which I've installed, uninstalled, and then re-installed as of last night) and VLE. I have also been able to convert .mov files into .mp4 from VLE, but never able to import those into this version of Premiere. These particular files do not have any kind of camera attached to them, as they were originally exported from animation programs (TVPaint, specifically), but I've been able to import stuff from there in previous Windows versions of Premiere.
Yup, thanks. I didn't know about this until today, as I've been much busier with other things and in other non-Adobe programs. I ended up parallel-installing 2017, exporting the project as an XML, and then opening that in Premiere Pro 2017. Files import there perfectly.
For those of you still having trouble with this after updating software, reinstalling, renaming or even trying to convert good files which won't import, use Media Encoder CC. I was one of those that did everything and this fixed the issue. Imports like a breeze now. Good luck!
Just created some screen capture videos using the latest version of QuickTime. Premiere Pro CS6 has no trouble importing them. However, the latest version of Premiere Pro CC 2018 will NOT import them. It just throws this error message. Why is it that developers spend so much time "improving" software, but more often than not, break something in the process? Clearly, I was not using QuickTime 7 era formats and codecs as was mentioned above.
Thanks for the reply. Appreciate it. It's amazing how quickly obsolescence occurs in today's world. The Buddhists have it right: embrace impermanence and find contentment. Pretty soon phones, plug-ins and partners will last a month. Om mani padme Om!
I had to go the OTHER direction - renaming from mp4 to mov, oddly enough. I shot 65 clips on the same camera with the same settings on the same day and 15 of them, randomly dispersed through the directory, wouldn't import until I renamed them to .mov 's.
As you guys figured out, the problem is with the codecs, in that Premiere Pro no longer supports QT7. The easiest way around is to simply use something like VLC to transcode the problematic video file and replacing footage in Premiere with the new format. Easiest fix I've found, isn't really a fix, its a workaround.
Thank you, Adobe!
Anyone know why they discontinued the codec and format? Memory leak, security?
No. Adobe did not make that decision on its own. Apple did. You see, QuickTime is an Apple origination, and Apple itself had pulled the plug on all of its 32-bit codecs for support. That required everybody that relied on those codecs to also yank support for them as well. All future QuickTime codecs must be completely 64-bit compliant. Which those older codecs NEVER were.
Thank you, RjL190365. Oh, well, like I said, just work around the issue. Sure, a pain in the butt at times, but at least we have options. Would be worse if we had no options, meaning and all support for those old codecs and formats no longer worked at all, in essence, forcing us to keep our old machines running in order to make changes to our old video production files.
I guess my, "Thank you Adobe" isn't all that well placed, for I really do thank Adobe for making things AWESOME! Makes my job so much easier in producing quality content! No jab at them at all.
I have been facing the same issue, while I import my file to premiere it dont have audio. Or the file scratched means don't play smoothly. Then I want to post here new thread just saw this thread on community. Now everthing is good. Actually, I came to know that there was error in importing the file my sports vlog that was recorded with camera.
In case anyone still having sound issues with imported MOV files. I was able to import the .mov file, then immediately export as .mp4. That new file, when imported, plays correctly. . . sound and all.
The specific ones Im trying for my current project are exports from AE , rendered lossless animation .mov , worked fine in CS6 , will play in quicktime and other generic's but always getting the The FIle Has no Audio or Video Streams message when trying to import into a project.
I'd tried that, didn't work for me, I think it was a clash with sorreson for me, I reinstalled is and all progs apart from squeeze and have no issues now, when I've got time to do a recovery point and test it out i will, right now got to much work to spend time on it
I had a .mov file - with no audio - on a timeline for a few days then I re-opened the project and the clip was showing as off-line. Tried to re-link it but got the message: The File Has no Audio or Video Streams - tried everything, then decided to try re-naming the file - changed .mov to .mp4 - voila! it worked! Worth a try.... ?
- Check the media cache location under Preferences > Media Cache
- Then navigate to that location via Windows Explorer
- Quit Premiere Pro
- Delete all the files from these folders: Media Cache Files, Media Cache, Peak Files and PTX
- Relaunch Premiere and create a new project
- Import the MOV files
Here's yet another possible solution (the file rename didn't work for me). I happened to install QuickTime Pro (7.7.6) so I could add an audio track to a video-only .mov as suggested above. After the install and before I added any audio, the problem was resolved. I could see the .mov previews correctly in the AP Media Browser (they were just icons before that) - and they imported just fine.
I had the same issue, what I did was import the video file into a Adobe Audition and then export it back into Premiere with Dynamic link that worked quite good for me, at least while I find a final solution to this bug.
I'm having same issue, PP 2015 CC will not recognize mov animation file, it is an intermittent issue because it worked before and now it's telling me there is no audio or video stream. So far I see no fix, never had this issue with CS6. Adobe: I don't understand why you update somethings in CC but lose certain functionality, like this? If it's not broke, don't fix it....well, in this case you break it. Can you please create a patch for this?
I tried installing older versions of QuickTime, reinstalling Adobe, uninstalling lots of video programs (such as K Lite Codec Pack etc). I upgraded Premiere 2014 CC to 2015 CC which made some good - as Premiere 2014 didnt even start, hanging on some ExporterQuickTimeHost.prm forever and than terminating. Now it steps for a while on loading this prm file on start, but then proceeds. I guess Premiere 2015 sees the same error but just skips, and cannot work with QuickTime after that. I've read lots about this bug being connected to other software blocking Premiere's TCP communication to QuickTime but cannot find where it can be broken.
I just installed the latest update to PP CC 2015, and the next day, all my AE imports were offline. Tried relinking and got the same "no video or audio streams" error everyone else is having. They were exported with the Animation codec with lossless and lossless with alpha preset. When I re-exported the clips as ProRes 422, voila! They imported perfectly.
I had older .mov files with alpha that just didn't load up - they relinked just fine. I tried to import new .mov files with alpha without success - after deleting the media cache they loaded as well. Thanks!
I think the solution is very simple, I made the Premiere Update for this year, then when I tried to open a project made in the previous version Premiere transfer all those files to the new version, at that point is when my .mov files went offline so what I did was close Premiere, restart the computer, reopen Premiere, then open the project that was converted and problem solved, all my .mov files are online again, so in my opinion, it's like when many softwares have updates you need to restart the computer to make the updates work. It works for me, hope that can help.
I uninstalled and reinstalled Quicktime, which resolved the issue temporarily. The footage was imported and working well until I closed and reopened the project. Seemingly at random, the footage went offline and is delivering the error code.
Update: My Desktop running version 9.1.0 (174) build, is able to load the same project without issue. Though it does disconnect the media each time I close and reopen the project. The same Quicktime files won't load 9 out of 10 times I open the project on my laptop running 9.1.0 (174) or 9.2.0 (41).
The problem was that Premiere Pro seems to be confused about whether the file has an audio stream. If it doesn't, then it seems to assume that it doesn't have a video stream either and throws the error. Ensuring that the MOV has both a video and audio stream fixes the problem
I would like to confirm that for me, clearing the Media Cache and restarting Premiere Pro worked. I managed to re-link the videos in bulk after doing so. For individual videos that become unlinked, renaming the file works as well, and doesn't require you to restart the program.
I definitely advise people to try to clear their Media Cache first, as Apple announced that they are deprecating QuickTime for being potentially vulnerable to malware. Only try installing QuickTime if it doesn't work.
The issue - this file has no audio or video streams - can be caused from many reasons. Based on the information that we have collected from our users and the online forums, there are two big ones which could lead to this problem.
d3342ee215