Graphics card: Onboard, min. resolution 1280 x 1024, 512 MB VRAM and DirectX 11 support (recommended: Intel Graphics HD 520 for MPEG2/AVC/HEVC)
It is really unfortunate that the specification wordings are really not clearly expressed.
For me, an extra sentence.... "Hardware encoding supported only by Intel HD graphics" ...... or better still "Nvidia and AMD hardware encoding not supported".... will definately make it crystal clear. But then may be they do not want to really mention that due to marketing reasons.
In any case, one can always edit and make a video in MEP and export it to some raw format, then use another FREE tool that uses the Nvidia 1050 build-in H.265 encoder to encode HEVC, if you really need H.265. Takes additional task outside MEP and 15 mins (well it depends on your video length). No biggy at all.
Alternatively, just use another free video encoding tool like DR. Well that come itself comes with another set of issues.... Fusion is just too complicated for simple stuff used by a home video users.
Here's media info on one of the clips. Unfortunately that does not show enough detail. See the note at the bottom of the screenshot where it say "Note - for more information about the file......." - please select the "Text View" from the View menu and copy and paste the info into you post.
General
Complete name : C:\Users\Eric\Videos\IQ\The Way We Burn\Cam 2\MP4\Bikes - Tim-Brad\00002.mp4
Format : MPEG-4
Format profile : Base Media
Codec ID : isom (isom/iso2/avc1/mp41)
File size : 7.93 MiB
Duration : 13 s 560 ms
Overall bit rate mode : Variable
Overall bit rate : 4 909 kb/s
Writing application : Lavf54.63.104
Video
ID : 1
Format : AVC
Format/Info : Advanced Video Codec
Format profile : Main@L4
Format settings : CABAC / 1 Ref Frames
Format settings, CABAC : Yes
Format settings, Reference frames : 1 frame
Codec ID : avc1
Codec ID/Info : Advanced Video Coding
Duration : 13 s 560 ms
Duration_FirstFrame : 40 ms
Bit rate : 4 753 kb/s
Nominal bit rate : 4 496 kb/s
Width : 1 920 pixels
Height : 1 080 pixels
Display aspect ratio : 16:9
Frame rate mode : Constant
Frame rate : 25.000 FPS
Color space : YUV
Chroma subsampling : 4:2:0
Bit depth : 8 bits
Scan type : Progressive
Bits/(Pixel*Frame) : 0.092
Stream size : 7.66 MiB (97%)
Writing library : x264 core 129
Encoding settings : cabac=1 / ref=1 / deblock=1:0:0 / analyse=0x1:0x131 / me=dia / subme=2 / psy=1 / psy_rd=1.00:0.00 / mixed_ref=0 / me_range=16 / chroma_me=1 / trellis=0 / 8x8dct=0 / cqm=0 / deadzone=21,11 / fast_pskip=1 / chroma_qp_offset=0 / threads=8 / lookahead_threads=1 / sliced_threads=0 / nr=0 / decimate=1 / interlaced=0 / bluray_compat=0 / constrained_intra=0 / bframes=0 / weightp=2 / keyint=250 / keyint_min=25 / scenecut=40 / intra_refresh=0 / rc_lookahead=40 / rc=abr / mbtree=1 / bitrate=4496 / ratetol=1.0 / qcomp=0.60 / qpmin=10 / qpmax=51 / qpstep=4 / ip_ratio=1.41 / aq=1:1.00
Codec configuration box : avcC
Audio
ID : 2
Format : AAC LC
Format/Info : Advanced Audio Codec Low Complexity
Codec ID : mp4a-40-2
Duration : 13 s 504 ms
Duration_FirstFrame : 64 ms
Bit rate mode : Variable
Bit rate : 165 kb/s
Maximum bit rate : 192 kb/s
Channel(s) : 2 channels
Channel layout : L R
Sampling rate : 48.0 kHz
Frame rate : 46.875 FPS (1024 SPF)
Compression mode : Lossy
Stream size : 272 KiB (3%)
Default : Yes
Alternate group : 1
Hi
Thanks for the Media Info. That looks pretty typical of the material that most MEP users would be working with, so nothing jumps out there. However being AVC H.264 it would still be utilising the the Intel GPU Quick Sync hardware layer for on the fly decoding / encoding of the timeline during playback of transitions and effects. Very low bitrate for Full HD.....
Peter
I'm going to side with PCS800 here. Magix has been (probably not deliberately) vague about how MEP uses graphics cards. Given the plethora of high-end card options there are and why they are used, it would be reasonable ot assume that a graphics program like MEP would use the latest and greatest external card. Fair enough that it doesn't, but Magix should shout it out in plain language, because it is not logical.
I'm just mighty relieved that I have read these performance threads; I am considering an upgrade and probably would not have specifically considered the iGPU "requirement", based on the published specs.
Thanks to everyone for trying to help. My work around is this.