User:Thompsony/draft/sys req: Difference between revisions
No edit summary |
m (minor formatting) |
||
| (One intermediate revision by one other user not shown) | |||
| Line 3: | Line 3: | ||
People has reported success in editing projects with 2GB ram and atom processors. The exact requirement depends on the project, but it should scale with most CPUs. Your mileage may vary. | People has reported success in editing projects with 2GB ram and atom processors. The exact requirement depends on the project, but it should scale with most CPUs. Your mileage may vary. | ||
User with older systems are encouraged to use the <menuchoice>Project -> Project Settings -> Proxy Clips</menuchoice> and adjust the dimension for your needs. | User with older systems are encouraged to use the <menuchoice>Project</menuchoice> -> <menuchoice>Project Settings</menuchoice> -> <menuchoice>Proxy Clips</menuchoice> and adjust the dimension for your needs. | ||
{{Note|1=Proxy clips are lower resolution clips exclusively used during the editing process while lowering cpu and ram usage. Upon rendering the original clips are used. }} | {{Note|1=Proxy clips are lower resolution clips exclusively used during the editing process while lowering cpu and ram usage. Upon rendering the original clips are used. }} | ||
| Line 11: | Line 11: | ||
Support for Nvidia GPUs can be spotty due to the proprietary nature of the driver. AMD GPUs are not supported on linux at this point. | Support for Nvidia GPUs can be spotty due to the proprietary nature of the driver. AMD GPUs are not supported on linux at this point. | ||
The windows version has hardware acceleration included. For | The windows version has hardware acceleration included. For Gpu acceleration on linux, both MLT and ffmpeg need to be compiled with gpu encoding flags. See [https://trac.ffmpeg.org/wiki/HWAccelIntro HWAccelIntro] for further information. | ||
To check if your MLT and ffmpeg installation supports gpu acceleration, run | To check if your MLT and ffmpeg installation supports gpu acceleration, run | ||
{{Input|1=<nowiki>melt -query "video_codecs" </nowiki>}} {{Input|1=<nowiki>ffmpeg -encoders</nowiki>}} and look out for h264_nvenc and hvec_nvenc. If none are listed, your installation does not support gpu encoding | {{Input|1=<nowiki>melt -query "video_codecs" </nowiki>}} {{Input|1=<nowiki>ffmpeg -encoders</nowiki>}} and look out for h264_nvenc and hvec_nvenc. If none are listed, your installation does not support gpu encoding | ||
Latest revision as of 12:00, 15 March 2019
System Requirements
People has reported success in editing projects with 2GB ram and atom processors. The exact requirement depends on the project, but it should scale with most CPUs. Your mileage may vary.
User with older systems are encouraged to use the -> -> and adjust the dimension for your needs.
GPU support
Support for Nvidia GPUs can be spotty due to the proprietary nature of the driver. AMD GPUs are not supported on linux at this point.
The windows version has hardware acceleration included. For Gpu acceleration on linux, both MLT and ffmpeg need to be compiled with gpu encoding flags. See HWAccelIntro for further information.
To check if your MLT and ffmpeg installation supports gpu acceleration, run
melt -query "video_codecs"
ffmpeg -encoders
and look out for h264_nvenc and hvec_nvenc. If none are listed, your installation does not support gpu encoding