How to update graphics driver to solve some crash issues in Filmora?
The graphics driver is a system software that controls a computer's video adapter (sometimes called a graphics card or GPU). Updating the graphics driver can correct some odd visual behaviors in Wondershare Filmora, which includes, but are not limited to, the following:
-Starting crash issue related to GPU driver
-Video lags while editing
If you have similar issues listed above, please try the following steps to update your graphics driver.
Before updating your drivers, you need to know what graphics card your computer processes. Here are two methods for you to identify. Use the DirectX Diagnostic Tool
(1) Choose Start, type dxdiag in the Search text box, press Enter. A window will pop up.
(2) Select Display tab, your graphics card name, manufacturer, version and date will now be displayed.
Based on your graphics card, you can choose the link below to update your driver. Generally, Filmora suggests you to download the most recent driver version that is available.
(1) Nvidia users can download the latest drivers from: https://www.geforce.com/drivers
(2) AMD/ATi users can download the latest drivers from: https://www.amd.com/en/support/kb/faq/gpu-driver-autodetect
(3) Intel users can download the latest drivers from: https://www.intel.com/content/www/us/en/support/detect.html
NOTE: If you have a notebook or laptop computer, you should visit the website of the notebook manufacturer to download the latest driver. Here is the link for your reference.
Can I use the built-in effects in Filmora9 commercially?
effects (titles, transitions, filters) are designed in house, you are allowed to use in any commercial project. While music is out sourced from 3rd party vendor and licensed for non-commercial use ONLY.
How to take a sample in macOS when my Filmora9 freeze or crash?
When you face the freeze or crash issue during editing with Filmora, please take a sample and send to us to do further troubleshooting here.
If Filmora app becomes unresponsive (“hangs”, “spins”, or “beachballs”), a sample of the app process will help us figure out why. To take a sample, open the Activity Monitor application (from the Utilities folder inside your Applications folder).
Attach this file to a message to our support team describing what you did directly before the app locked up, and we’ll do the rest!
An Activity Monitor sample is a brief snapshot of everything an application is doing at that particular moment. When this snapshot wraps up, the resulting text file will display a few different things.
First, the header will state how many samples were taken, over how many seconds. It will also report some information about the application—like its location on your computer and version—as well as which OS you’re running.
The second section is a call graph, show what functions the target application was running at the time, and how many times they were run over the duration of the sample. The final section will show a list of all the frameworks your software uses. Frameworks are small sections of code shared between apps that can help perform common tasks.
So what’s this all mean? Tough to say, to the untrained eye! In many cases that snapshot will look pretty boring—our app is listening to the operating system, or the user interface might be doing its own thing. During a hang, we may be able to pinpoint the cause of a problem by isolating a particular function that’s getting stuck. Figuring all this out will be our job, though.
The only personal information that’d be included in such a report would be the Path for your application. If you’d like, you can check this for yourself before sending in the sample by looking at the information in the first few rows of the sample, before the call graph. The path will most likely be rather benign, like:
…which obviously doesn’t contain any information about you.
Browse HTML articles here to get great tips on web editing and other tech-related topics!