Slow playback in edit screen MEP2016 plus Windows 10

langford wrote on 12/17/2016, 8:32 AM

I have been editing a movie on and off for several weeks without any problems. On opening the prog recently for further work I find playback will not run in real time.I can make it run in real time by use of tha slider held at 1.00

It has been suggested that a Windows 10 update may have affected the GPU driver, in my PC this is GTX 650.

I have checked for current driver updates through Windows which shows driver OK. The problem suggests to me some form of change in settings but to my knowledge I have not made any changes.

Would appreciate some advice.

langford.

Comments

Scenestealer wrote on 12/19/2016, 3:03 AM

Do not rely on Windows update for Graphics driver updates or info. Go to the PC or Graphics card manufacturer's website and manually download and install the latest driver.

langford wrote on 12/22/2016, 8:42 AM

Scenestealer

Thank you for your suggestion regarding GPU driver update. Ihave updated my driver from the Navidia web site but this appears not to have solved my problem.

Any other suggestions.

Regards

langford.

Scenestealer wrote on 12/22/2016, 3:34 PM

You could try going to an earlier restore point in Windows to confirm if an update had caused the problem, or go to "File > Settings > Reset program setting to defaults" to see if you unwittingly changed a program setting.

langford wrote on 12/30/2016, 9:55 AM

Scenestealer

Thank you for your last comments. I have now resolved the problem, it appears the driver update did not fully install.

I am beginning to regret upgrading to Win 10 as yet another problem has developed as a result of a recent up date, I now have no E drive ! - will it never end.

Thank you for your interest.

Regards

langford

johnebaker wrote on 12/30/2016, 12:13 PM

. . . as a result of a recent up date, I now have no E drive ! - will it never end . . . .

From experience so far with Windows 10 upgrade and updates - not for a long while - Microsoft seem hell bent on altering user security privileges on a regular basis at the moment which can cause all sorts of issues.

E: drive

If this is an internal hard drive (HD) - make sure you have no external USB device, such as a memory stick or HD plugged in, it may have taken over the E: drive assignment and is stopping the HD from starting.

If it is an external USB drive - unplug it and fully shut down the PC. Restart the PC and give it a few minutes to settle down after logging in, then plug in the USB drive again - it should be detected.

If not then right click the Computer icon on the desktop and select Manage.

Open the Device Manager section and select the Disk drives entry - does the E: drive appear there with a yellow exclamation mark against it? If so right click and and select Uninstall.

Right click the very top entry - this should be the computer name - and select Scan for hardware changes - the HD should be detected.

Note if you manually assigned the drive letter to the E: drive it is best practice to assign drive letters from Z: downwards - this stops drive letter conflicts for devices such as external USB HD's, memory sticks etc.

Please note that any changes you make in Device Manager are at your own risk.

HTH

John EB

langford wrote on 1/7/2017, 8:37 AM

John

Thank you for your response of 12/30/16.My E drive is my DVD/Blue-ray writer and until a recent WIN 10 update was working fine.I now have error code 52 indicating Windows will not recognise the driver for this device - digital signature problem.There is lots of advice on the web. as to how resolve the problem. As I have limited computer experience I tend to try options that appear straight forward. I have tried the driver up date option even though Windows troubleshooter indicates driver is up to date

I have down loaded an updated driver file from the manufacturer but it will not install " ATAPI device cannot be found ".

Can you offer any assistance.

Regards Langford.

johnebaker wrote on 1/8/2017, 2:16 AM

. . . . My E drive is my DVD/Blue-ray writer . . . .

This could be a difficult one to resolve however as a first step try steps 3 to 8 only in this tutorial.

If this fails to fix the problem then see this Microsoft article. My preferred option would be to try Resolution 4 first - this often works before the others, in particular editing the registry.

Note editing the Registry requires care and you do so at your own risk.

HTH

John EB