-
Cannot import MOV ProRes into Vegas Pro 13
Posted by Mateusz Duzinkiewicz on July 31, 2015 at 12:05 pmHello my friends.
Got problem with MOV ProRes files :/ Got the newest 7.7.7 QuickTime player so automatically there should be also ProRes decoder for Windows (got Windows 8.1 x64 with all updates) but when I try to import it to Vegas, Vegas says:
“Stream attributes could not be determined”
I uploaded small file to FTP so please download it and see your self, maybe you could figure it out what’s missing?
https://mega.nz/#!ohsyHDAL!5O_7tj8ettzWwWqnolwEoo46iNW0-NN1EEgptkgUCgs
Please help ASAP 🙂
Steve Rhoden replied 11 years ago 4 Members · 13 Replies -
13 Replies
-
John Rofrano
July 31, 2015 at 1:12 pmSame problem here. I’m on Windows 7 64-bit with QuickTime 7.7.7 and Vegas Pro 13.0 Build 444 and all I get is Audio. When I open the file in QuickTime Player and look at the Inspector Windows (Ctrl+I) it says ProRes 422 LT 1920×1080.
I then loaded your ProRes file into Apple Compressor and then rendered it as ProRes 422 LT and the rendered file worked fine in Vegas Pro 13.0. So there is something abut the ProRes file that you have that seems to be non-standard. Was it created with a licensed encoder?
Bottom line: Something seems to be wrong with that file. Where did you get it from?
~jr
http://www.johnrofrano.com
http://www.vasst.com -
Mateusz Duzinkiewicz
July 31, 2015 at 2:35 pmMy producer claims that files ware copied from Fs700. It’s hard to believe that Sony Fs700 creates files uncompatible with SONY’s own NLE system :/ Is it possible?
-
Mateusz Duzinkiewicz
July 31, 2015 at 2:58 pmUPDATE – the file was converted from original format in to ProRes by Adobe Media Encoder 2015 so clearly it is ADOBE compressor fault. Anybody should inform ADOBE about that bug? Or maybe they did it on purpose? What do you think?
-
Mateusz Duzinkiewicz
July 31, 2015 at 5:02 pmThere is no point in installing it, it was created in 2008 and now it is merged with QuickTime Player installer so if you have newest 7.7.7 Quick Time Player installed you will be unable to install ProRes Decoder, system won’t let you do it. Anyway thanks for bringing it up 😉
-
John Rofrano
July 31, 2015 at 7:27 pm[Mateusz Duzinkiewicz] “UPDATE – the file was converted from original format in to ProRes by Adobe Media Encoder 2015 so clearly it is ADOBE compressor fault. Anybody should inform ADOBE about that bug? Or maybe they did it on purpose? What do you think?”
That makes more sense. I wonder if it was encoded on a PC or a Mac since Adobe Media Encoder runs on both. I’m guessing it was the PC version because the Mac version would have probably used Apple’s encoder.
So what was their plan? They have a Sony camera that shoots AVCHD that Vegas Pro edits like butter and they convert it onto a Apple format. What were they thinking? Obviously they didn’t plan on you editing it on a PC in Vegas Pro because the native camera format would have been the best format for you and it would save them a generation of re-encoding.
As I said, you can re-encode them with Mac Compressor if you need ProRes 422 files that Vegas Pro can edit but if I were you, I’d ask them for the original camera files because that’s what you want to be editing with Vegas Pro.
~jr
http://www.johnrofrano.com
http://www.vasst.com -
Steve Rhoden
July 31, 2015 at 11:35 pmAdobe media encoder added that problematic twist!
Steve Rhoden (Cow Leader)
Film Maker & VFX Artist.
Owner of Filmex Creative Media.
Samples of my Work and Company can be seen here:
https://www.facebook.com/FilmexCreativeMedia -
John Rofrano
August 1, 2015 at 11:02 am[Steve Rhoden] “Adobe media encoder added that problematic twist!”
wasn’t that nice of them. lol 😉
The bigger questions is why would you re-encode your camera footage into ProRes 422 LT? There s only one reason I can think of and that’s because you expected to edit it on a Mac. So why is it being edited on a PC in Vegas Pro? It’s not going to go well because Vegas Pro doesn’t handle lots of QuickTime files. It blows up. So this might not end well. Very confusing workflow.
~jr
http://www.johnrofrano.com
http://www.vasst.com -
Mateusz Duzinkiewicz
August 1, 2015 at 11:18 amTechnically speaking, files was re-encoded by my producer from some kind of low compression (heavy in MB) compression to lighter format (so they can work online with me) and because they use Apple version of Adobe CC so they automatically re-encoded files to MOV ProRes LT. Next time I will suggest them to re-encode to MP4 H.264 😉
-
John Rofrano
August 1, 2015 at 1:08 pm[Mateusz Duzinkiewicz] “…files was re-encoded by my producer from some kind of low compression (heavy in MB) compression to lighter format (so they can work online with me)”
This is really important: If they are using Macs and they want to work with you, and you want to work on a Windows PC with Vegas Pro, they should NOT use any QuickTime formats. Vegas Pro does not handle QuickTime well in large projects. At around the 100 clip mark Vegas Pro runs out of memory and you will be very unhappy. Like I suggested, you want to be editing the original files from the camera with Vegas Pro. If they insist on using QuickTime you need to be very mindful of how many files you add to a project.
[Mateusz Duzinkiewicz] “…because they use Apple version of Adobe CC “
Wow, so Adobe messed those files up on a Mac. That’s surprising. I would suggest they use Apple Compressor to convert the files next time. When I converted the files with Apple Compressor they played fine with Vegas Pro and the best thing is… Apple Compressor only cost $49 and you own it forever! 😉
BTW, I loaded your ProRes file into Final Cut Pro X on my Mac Pro and it played fine. So only Vegas Pro seems to have problems with these files but it has no problems with Apple Compressor ProRes files.
[Mateusz Duzinkiewicz] “Next time I will suggest them to re-encode to MP4 H.264 ;)”
No, next time ask for the original camera files because your Sony software works great with Sony camera files! You don’t need them to re-encode anything.
So how are you going to work with them if they are using Adobe and you are using Vegas Pro? Are you just delivering a final rendered product to them? I hope you don’t expect to share projects via XML (‘cuz that doesn’t work except for extremely simple one track projects with just cuts and dissolves). Just curious.
~jr
http://www.johnrofrano.com
http://www.vasst.com
Reply to this Discussion! Login or Sign Up