@johnebaker

 I am using the Nvidia Studio drivers version 462.59 (27.21.14.6259).

I'm on version 471.41 (30.0.14.7141 dated 12/07/2021) and using a GTX 1060 3GB.

Sev.

@SevCardy

Hi Sev

I have updated the drivers to the same version, I still get the same result - cannot replicate.

Forgot to mention previously - same VPX version.

What was the export time for a 5 second image?

John EB

@johnebaker

What was the export time for a 5 second image?

If no effects applied (and therefore working without errors), 1.8s according to the log.

If resized (and therefore errors in the log and a blank video output) 3.0s.

I can only assume the fact that you can see the image on the output file and I can't is down to the difference in GPU.

Bizarrely, if I place another image after the first (both without any effects applied), the export gets to the 5.01 (seconds.frames) point in the movie, pauses for a bit and then gives the "update your graphics driver" message on screen and in the log the messages:

2021/08/05 17:34:35 [FATAL]   [MPEGIntel]: DP4::IntelVideoEncoder::Encode: SEH exception 0xC0000005: access violation
2021/08/05 17:34:35 [FATAL]   [MPEGIntel]: EncodeError |DP4 errno=0x8000FFFF: Catastrophic failure
                               |buffer address=0x000000007F2AA380, size=40 |where=VideoEncoderBase::Encode called EncodeFrame
2021/08/05 17:34:35 [FATAL]   [MPEGIntel]: MP4Pipeline::EncodeVideo frame 128: HardwareEncodeError
2021/08/05 17:34:40 [FATAL]   [MPEGIntel]: EncodeError |DP4 errno=0x04100419: Error 1049: error waiting for completion event |buffer address=nullptr, size=0 |where=VideoEncoderBase::Encode called EncodeFrame
2021/08/05 17:34:40 [FATAL]   [Export - Engine]: Bounce: CInfoException: 0x8004002b - export->WriteVideoFrame

As far as timings are concerned I'm very impressed with VPX13 (when it works!). A 553.2 sec movie consisting of all UHD source material, no images, a simple title and only a small number of cross-dissolves, no other effects or processing, exports to HEVC UHD in 178.3 sec with no errors. Not bad for a 4-year-old computer! I was really beginning to think I could start using VPX13 in earnest for UHD work until I found this problem with images.

Sev

@SevCardy

Hi Sev.

Is it just at 4K you get problems. Can you export the same project at 1080p?

Ray.

@CubeAce

Hi Ray,

Yes, it exports fine at 1080p. No error messages and the resized image shows up in the output video.

Sev.

@SevCardy

Hi Sev.

I'm wondering if it is a lack of vram on the 3GB version of your 1060 nvidia card that is showing a difference between your and Johns results.

I'll bet anything to ninepence that Magix are testing using the 1060 6GB version. I think there are a few subtle differences between the two cards other than the mount of vram.

Ray.

@CubeAce

I'm wondering if it is a lack of vram on the 3GB version of your 1060 nvidia card that is showing a difference between your and Johns results.

I've been thinking along the same lines. It's a 4-year old one and not the later spec 1060 card. Frankly, I was surprised that it coped with exporting UHD video. I suppose re-sizing an image takes more memory. It should give up more gracefully though; VPX says the export has finished successfully, but the resulting video has missing images and the log shows fatal errors!

LATER ADDITION: Just checked performance monitor and the 1060 is shown as using only 1.8GB of dedicated GPU memory when processing the export to UHD. But I have discovered that resizing a video clip produces the same error as resizing an image (I don't do that very often, so I didn't think of trying it!), so it is definitely something to do with resizing, but only when when exporting to UHD.

Sev.

@SevCardy

Hi Sev.

The spec pages for VPX are still showing you should only need a 2GB card for 4K but 4GB for 8K but I'm wondering if the effects within VPX need tweaking and reigning in a bit or the specs are now wrong for whatever the infusion engine 3 is up to. The other thing John and I have discussed is the amount of rops and the pixel shading capabilities of various cards seem to have some sort of relationship to how successful an export is. As neither of us are software engineers we can only look at what various people seem to suffer and speculate.

Ray.

@CubeAce

The culprit is definitely setting processing = NVIDIA in the program settings. Setting that to Intel, CPU, or Warp works (although using Warp is phenomenally slow, taking 97.6 seconds for a 5-second resized video clip - 3 and a half times as long as using processing=CPU!).

So, to summarise, the combination of resizing an image or video clip and exporting to HEVC UHD with processing=NVIDIA gives errors every time for me.

Sev.

@SevCardy

Hi Sev. Sorry, which nvidia card are you using?

@MAGIX_Redaktion

On a separate note, has the 'Edit wave in external Editor' been fixed yet? Not sure what broke it but hasn't worked on VPX or MEP for some time now.

Ray.

@CubeAce

Sorry, which nvidia card are you using?

It's a GeForce GTX 1060 3GB, which came with my computer bought in 2017.

Sev.

Video Pro X 13 is not working for me! Continuous crashes. How can I revert to version 12? need a download link.

@Michael-Hubbs

Hi Michael and welcome to the user to user forums.

If you had VPX 12 previously loaded you can find the link here.

Ray.

OK Found it.

@MAGIX_Redaktion

Hi,

Size/Position/Rotation seriously needs work. I was trying to save and load effects that included putting the anchor point at the upper left of the window so that it worked as before, resizing to 50% (please put back the percent slider/box) as Effect1, bottom left (bottom aligned with bottom left). I saved each. I tried to set kfs, didn't seem to work right. Instead of beside the value, the kfs showed up below. I loaded the alternate effect, nothing happened. I ended up with this image:

What a mess. Maybe it was just today, so I'll try tomorrow. However, this effect needs serious work. I posted a list of what I would like to see under a MEP2022 topic. I'll post it here.

John CB

@browj2

Hi John.

I don't know if this has been fixed in MEP 2022 or not and I know we have different ways of working within the programs. Also I have not tried extensive use of the rotation handles as yet but I've just completed a small project using the size position tool a total of sixteen times within a 45 second video with no problems in either use or with the settings being saved.

Ray.

I AM HAVING SEVERE ISSUES WITH RESIZE/ZOOM/CROP... POS UPDATE HAS NOT RESOLVED THESE CATASTROPHIC PROBLEMS

@MAGIX_Redaktion @Michael-Hubbs @SevCardy @browj2 @johnebaker

1: I can no longer find this setting that allows for the quality of proxy files to be set.

Old system.

New System.

2: Even if I delete a project within MEP 2022 (including first deleting all clips etc within the project) and try to load a new one it still thinks a project is loaded. It asks if you want to delete the prior project (The one I though I had asked MEP to delete) or add it to the project. Adding the new project to the (deleted) old project opens the new project on its own.

3: The deleted project still comes up within MEP under File / 'Last opened disk project', and opens fully, including all previous deleted files.

Ray.

@CubeAce

Hi Ray.

Should your latest post here be in the thread about VPX 13 since, although you show a first screenshot from VPX, the problems seem to refer to MEP 2022?

If it should actually be in this thread perhaps you should repost it there and hide the post here?

Jeff

@emmrecs

Hi Jeff.

I will re-post in the MEP topic. I was going to when called for dinner 😇 but I am curious to know if the same problems / happen in VPX. Especially the lack of choice of proxy file settings which is still in VPX 11.

Ray.

@CubeAce

Hi Ray

The VPX setting have always been different to the 3 choices in MEP, with the Custom Settings opening up a raft of different formats and codecs, but I have not yet installed VPX13 or MEP2022 to confirm.

Is it possible that the setting is revealed after clicking the little lightning symbol drop down above the track headers?

Peter

Hi Peter.

That shot is taken from VPX 13. MEP 2021 had the same settings in the same parts of the main menus.

They are now missing or if somewhere else I can't find them.

Ray.