Microsoft has offline guine tests to use in such cases. I'm sure the support should be able to help you with this.

Correct. Mediacomposer is also optimized to make use of this extra RAM. The boot option allow you to choose to use the normal and the changed setup (to avoid conflicts with other applications)

And did you delete your old render files ? otherwise Liquid is maybe still using files from before you installed the patch. We did not get reports yet of rpoblems with iTunes. The only reason why I can think of a conflict is when improting or exporting quicktime files, as Itunes is quete integrated in Quicktime currentley. When using quicktime ...

There is free e-mail support for Liquid so you do not need to use your sac. Go to http://pinnacle.custhelp.com and put your question in the ''ask a question'' section. Make sure you select ''Liquid'' from the product selection otherwise the question ends up with the Studio support group.

Every generation of a reencode will loose some quality. it is probably not much, but there is no need for that in this workflow. The content on your timeline is MPEG-2, and in the end you want to create an MPEG-2 out of it. As liquid can edit MPEG-2 native you basically only need to render the effects. By rendering them to MPEG-2. immidiatley you ...

I have replied to your PM

I have seen the download somethimes causing problems when upgrading, especially when upgrading from old Edition or Premiere versions. if you keep getting the problem please send me a PM with all your serials (Liquid 7, and the version where you are upgrading from).

My idea as well. Not sure if the option was already there in 5.62. But basically when it hangs on rendering the menu this is the cause. d:\render\tmp\new sequence is the render file the software tries to create. You say the file is not there. Which means Liquid was unable to create it.   In some cases this kinf of problems where solved by ...

It is not a tested setup, but we see no problems yet. FYI, Studio 12 is tested with the i7.  

You encounter this problem in Liquid after installing Studio 12, or do you have the problem in Studio 12 ? If you have the problem in Studio 12, better place it on the Studio forum so other Studio users can help you further finding a solution for the problem.