Ericbowen
Forum Replies Created
-
I have not seen any of these issues but there are several things that can cause it. I will tell you that 12GB of ram and the 640GT card is likely not helping your cause. You really should get a 760GTX card and more ram. What model CPU do you have? What is your drive setup? Are you using an external drive to work directly from?
Eric-ADK
Tech Manager
support@adkvideoediting.com -
What version of Quicktime do you have installed? Please uninstall Quicktime after you install Mir and then install the latest version from Apple’s website.
Eric-ADK
Tech Manager
support@adkvideoediting.com -
https://www.blackmagicdesign.com/products/atemtelevisionstudio/techspecs
This will still be 1080i. The Atem TV Studio wont handle the 1080P.
Eric-ADK
Tech Manager
support@adkvideoediting.com -
Sounds like different Quicktime SDK versions were used by Miraizon and Premiere. I have seen this before when there is a common file share that gets overwritten to a version Premiere doesn’t recognize. Is this CC or older version of Premiere?
Eric-ADK
Tech Manager
support@adkvideoediting.com -
The amount of ram per core/thread really is comp specific. Depending on the frame resolution, layers/complexity, and FX this fluctuates greatly. What works with ideally with 6GB per thread may not work so efficiently on another comp. This also can change the amount of cores used by the multiframe rendering versus the AE application and other processes currently provisioned by AE. As a general rule though the greater the frame res and amount of layers, the more ram per core you need.
Eric-ADK
Tech Manager
support@adkvideoediting.com -
-
Pro Res should be fine with CS6. What bugs are a concern?
Eric-ADK
Tech Manager
support@adkvideoediting.com -
Remember the OS is handling the threading and scheduling for all applications such as editors like Premiere or FCPX without any cpu setting control. This is something the OS is designed to do regardless of whether an application has an option for that or not. The differences occur in the priority assigned to the applications and the interrupts for each application call. For example an input command from an application can have a much higher priority than a data execute command and so on and so forth. If the editor is continuing to work on other applications and the input latency starts becoming an issue due to the scheduling and time it takes to interrupt cores then leaving a core idle will often alleviate that. However if that application has a high enough priority and the background application has the correct status for executing data this is negotiated efficiently by the OS.
Eric-ADK
Tech Manager
support@adkvideoediting.com -
The editor is not running into issues with AE not completing the render or crashing. The issue is the amount of time compared to dual or quad core laptop. The OS moderates these interrupts and should not have any issues interrupting the cpu’s when needed for the OS or another app. By default this set to 0 likely on the laptops as well. Setting a CPU to idle for non use by the application just is slowing it down in this case not speeding it up. If an editor is running into issues with AE crashing then that is a setting to look at. If not then it wont change the results here.
Eric-ADK
Tech Manager
support@adkvideoediting.com -
Setting CPU’s to use on other applications to something other than 0 wont speed AE render queue time up. However set multi processing on and the ram per thread to 2 to 4GB and see how that works. The comp decides how much ram you need per thread but those are the normal settings for standard comps. Also a screen pic of OSX CPU threading meter would help identify what your seeing.
Eric-ADK
Tech Manager
support@adkvideoediting.com