Vegas 13 No Longer Sees Nor Renders QT Files

Desdinovah wrote on 8/7/2014, 4:38 PM

I recently bought and installed Miraizon's ProRes and DNxHD codec pack and shortly after installing it, Vegas 13 started having issues (I don't know if it's related to the Miraizon install or not).

I have both Vegas 12 and Vegas 13 (most recent build for both) installed. 12 loads and reads any and all .mov files and will render out to any and all QT formats, including ProRes and Avid. 13 will do none of those, though it did. If I try and drag an .mov file into a project, I get the "ban" symbol and the file won't import. If I try and use the Import Media function from the Files menu. 13 won't even SEE any .mov files; they literally do not exist for 13. If I load a different file and try to render it out as an .mov, there are no QT options in the Render As menu.

So far I've uninstalled and re-installed 13, uninstalled and re-installed different flavors of QT, uninstalled and re-installed the Miraizon package and nothing has made a difference.

To me, the next step might be to manually copy and paste the codecs into a place where 13 can see them (I'm assuming that 12 and 13 have their own locations for accessing codecs. If I'm wrong then this won't help). If anyone has an idea of where I should look, I'd love to hear from them.

As I said, 12 has no issues with anything QT or .mov, it's ONLY 13 that does. I've reached out to Sony tech support and despite a couple of weeks of back and forth, there's been no progress and despite repeated explanations of the problem, I'm not even sure they fully understand the situation (no disrespect intended if any of the folks helping me read this!). :(

I'm beyond frustrated. If anyone can help and has any ideas, I'd really appreciate it.

Thanks.

Comments

videoITguy wrote on 8/7/2014, 5:18 PM

I assume first you are talking about installing the non-USA sanctioned version of ProRes and Avid encoding that comes from the Miraizon product. -NOTE this comment because these are different plug-in calls than if you would have had just left QuickTime for ProRes decode on Win machine and the Avid DNXHD codec package. Yes, that's right no ProRes encode. So you have made the system work differently than the default practice.

That said, I hear you saying with everything on your system as it is the way it is - you have no fault with VegasPro12 build 770 - but not working concurrently in VegasPro13 build 373?????
This would point to something other than the disturbance alone caused by your installation process. In order to pull these codecs the individual apps like Vegas have to register what they see, so a huge guess is that your Windows registry entries supporting the VegasPro13 are not there.

And that said - I am relatively certain that you need to follow this install order on a Windows base system that is absolutely clean - install Quicktime first, install Miraizon second, and finally install VegasPro. Do you have any other apps that are registering with Quicktime - especially the last versions of ProShow by Photodex or ??? what else?

Desdinovah wrote on 8/7/2014, 5:42 PM

Thanks for jumping in.

You're correct that Vegas 12 has no issues with QT but Vegas 13 can't see anything QT or .mov. You're completely correct about the install order needed with Miraizon and I tried several clean installs following that order and nothing in 13 has changed. 12, continues to see any and all .movs and renders to any and all .mov formats.

I completely agree that 13 just isn't getting the info it needs but I'm at a loss as to how to point it to where it needs to look.

*EDIT: Sony suggested I do a manual reset and it worked!! Yay! Thank you Eric D. at Sony for finding the solution!! You rock! :)

murk wrote on 8/27/2014, 11:00 PM

How do I perform a "Manual reset"?

** UPDATE 1
Ahh, hold CTRL+SHIFT and double click the Vegas Video executable. THen choose to delete all data.

This fixed one issue, I can now see "MOV" file when importing media, but Vegas still refuses to open the MOV (Animation codec)

** UPDATE 2
I Also needed to change the application to Always run as Administration, then did the manual reset as administrator. I can now open the MOV files. Hooray!

(Note to self, I also set the Comapatibility mode to Windows 7 at the same time as setting to administrator, but I do not believe that is what fixed the problem as I then turned off compatibility mode and it still worked)

I am experiencing a very similar issue. QT videos will not open Vegas Pro 13, but open fine in Vegas Pro 12. And here is the kicker, VV 13 in a different user account (both accounts are administrators) opens QT fine. What I notice is that the VV13 in the doesn't even see files with the "MOV" extension.

Len Kaufman wrote on 12/28/2014, 8:31 PM

I was having the same problem with SVP 13 producing Quicktime Error. SVP 13 wouldn't import any .mov files.

Spent a good part of a day trying to solve the problem. Removed and re-installed Quicktime. Same result. Finally, decided to attack the problem by looking at the problem from the QT side. I deduced that the problem was QT. I uninstalled QT and in its place I installed Quicktime Alternative. Free and available here:
http://download.cnet.com/QuickTime-Alternative/3000-2139_4-10633500.html

End of problem! Whew!

Arthur.S wrote on 12/29/2014, 6:39 AM

Just tried QTA Len, doesn't seem to install a player. To anyone else, it also downloaded and installed a couple of other 'freebies' even though I selected to decline them.

Christian de Godzinsky wrote on 12/29/2014, 3:21 PM

Len,

My sincerest thanks to you LEN!!! You made my day. I could kiss your toes...

I have been sending crash reports to SCS about the same problem and really hitting my head and pulling hair from the same. VP13 b428 does not like Apple's QuickTime. I have loaded the latest version that seems to be even more problematic. All other file formats behave well on the timeline but MOV files just turns out or shows black, both thumbnails and preview, rendering editing impossible.

THANK YOU for the alternative QT substitute. It works reliably, but renders preview video somewhat slower that the genuine QT. However, I can now edit.

SCS - please do something ASAP. The situation is unbearable.

Cheers,

Christian

videoITguy wrote on 12/29/2014, 5:04 PM

Before a lot of blame is cast in all directions - you should know that most users of VegasPro13 and all other versions of VegasPro for that matter have Quicktime on their systems.

Those who report problems and then quickly throw stones - should look at themselves in the mirror in (the glass house?). Your system lash-up is not correct. This could include install sequence, helper files, and other Quicktime related app installs. Then you get a tempermental beast as you observe. Quicktime certainly won't fix your install and neither will SCS.

Christian de Godzinsky wrote on 12/30/2014, 2:01 PM

Hi,

I left on purpose out all details about re-installs etc. VP is the only application that causes problems with QT. I have re-installed both. I am not the only having trouble with MOV files in VP13. Just search the forum. I don't blame SCS, the culprit might be @ Apple. But why does all other applications work fine with QT? I think it is SCS's responsibility to sort out why QT gives problems. For now the QT substitute works like a charm. It was my lifesaver and now VP works with MOV files with zero problems. I have looked in the mirror and not found anyone guilty... But I see a frustrated person that has lost valuable time and countless of hours trying to find a workaround to get a "pro" application to work as advertized...

Christian

videoITguy wrote on 12/30/2014, 3:35 PM

QT is a different animal - Apple controls its deployment. SCS has nothing to do with it.
Apple can do whatever they want, and in countless episodes in history they have overshot the bow many times so that Microsoft either had to catch up or get lost. It was an old war game if you will.

Vegas is no more sensitive a Microsoft platform app than say ProShowGold by Photodex with the QT install. All of these interconnects with Apple have problems. The installation can be worked out - but it is meticulous example of finding the right balance.

Len Kaufman wrote on 12/30/2014, 6:57 PM

Being the pragmatist that I am, I really don't care who's at fault. I needed to edit, and I needed a solution. I wasted a good part of a day trying to research and sort this out. Quicktime Alternative was the solution for me.

GeeBax wrote on 12/30/2014, 9:16 PM

I can't get Quicktime to play back anything of real interest, except the most basic of MOV files. It fits, starts, stops, freezes up and generally behaves badly.

Apple software sucks.

videoITguy wrote on 12/31/2014, 12:53 PM

On the contrary I have been using Quicktime since Version 3.0 a long time ago. Always load the pro version, keep it current with the mainstream apps, use Windows OS as appropriate. Load all kinds of .mov container from pro productions, DSLR, other oddball sources, and yes inside of VegasPro without a hitch. Thru VegasPro13 build 373.

Wolfgang S. wrote on 1/1/2015, 7:02 AM

Quicktime (or an alternative) must be installed for Vegas to run. But Quicktime delivers old routines only. So for the new 10bit 422 ProRes HQ Shogun files it is no really worse. Vegas crashes here when you import more then 20-25 files in the timeline - with less files it works so far. That is something that seems to be a Vegas bug, since I do not see that behaviour in Edius 7.41.

The next bug is that Vegas interpretates the luminance in a wrong way - so a file with 16..235 is seen as 0..255. That is a wellknown bug with Quicktime in a lot of applications.

The next point with the outdated ProRes decoder in Quicktime is that the decoder is to slow with my i7 2600K overclocked to 4.2 Ghz. In Vegas we see a very slow preview behaviour (6-8 fps only from 24p files), in Edius the buffer runs low. So we need faster processors to decode the old ProRes in 4K - what is crazy since that should not be necessary.

Adobe user are also fine with these files - since Adobe has developed an own decoder routine for ProRes.

So there are a lot of points that could be done to ensure that ProRes works fine in Vegas.

videoITguy wrote on 1/1/2015, 11:37 AM

I agree it is easy to point a finger at Apple ProRes as difficult codec. They are responsible for that. Packaging it inside .mov container is not the same issue as overall blame cast on Quicktime system.

If you look at the hardware and software going into support Apple ProRes you can appreciate what a problematic codec it is from a lot of points of view. Then using a non-official broadcast ffmpeg encoder to do encoding on Win OS is yet another story.