There are some users experiencing very long delays in some window operations on systems with Haswell CPUs and GTX7xx GPUs running Win 8.1. For me, the simplest test is to see how long it takes for the Modify/Stand-alone Effect window to open on Pixelan effects or transitions.
Pixelan is aware of the delay problem and their testing indicates it's an editor issue on specific hardware and/or with specific settings. They informed CL of the issue about 3 weeks ago, but since the 2 beta patches since then and now the latest 2706 release still haven't addressed the problem, I wonder if a few people would be willing to try a quick test on their systems.
You don't have to have any Pixelan effects installed to do this test. If anyone is willing, here are the steps:
How long does it take for the window to appear?
On unaffected systems, I imagine the window would open in a couple of seconds but it takes 7-8 seconds for mine to come up. On a more typical project with lots of clips and transitions, it takes more like 14 seconds. I would greatly appreciate any feedback you guys can give. Be sure to delete the CES_PlugInExample.dll and .xml files from the Shared files subfolder when you're done
Filename | TestPlugin.zip |
|
Description | PD12 menu test files |
|
Filesize |
15 Kbytes
|
|
Downloaded: | 669 time(s) |
This message was edited 3 times. Last update was at May 15. 2014 17:11
YouTube/optodata
DS365 | Win11 Pro | Ryzen 9 3950X | RTX 4070 Ti | 32GB RAM | 10TB SSDs | 5K+4K HDR monitors
Canon Vixia GX10 (4K 60p) | HF G30 (HD 60p) | Yi Action+ 4K | 360Fly 4K 360°