How do I get VPX to use more of my PC's capability? 7 hours rendering time for a 14 minute 4K 30 FPS MP4 on my machine specs (see my signature below) must be abnormal. Can anyone please provide some tips?
Thanks.
Hi Wayne.
Apart from the explanations we gave in your last topic there is a question of which and how many effects are being used. Does for instance the the project render speed up and down at varying points during the render?
Some effects can really slow down an export. I can name a couple off of the top of my head but there are more.
Image stabilization; noise reduction; any re-scaling of video such as picture in picture. Combining certain effects onto a single clip is even worse.
Try putting the same clips together with just simple cross-fades as an experiment. Even my humble setup can export 4K at at speed less than playing the file back. Try setting the export for Best in the advanced portion of the export and make sure the use GPU for rendering box is ticked.
I think it should render in less time than the total playing time of the project. If you are still on VPX 11 then make sure you have the following settings for program settings and exporting.
Other settings in the other tabs are not that important for this.
For MP4 export.
Ray.
Thanks Ray! There are no effects in use at all, and the timeline is just cross-faded clips, with added music tracks. Absolutely nothing special. If I use the GPU acceleration, VPX will crash on rendering. My export settings look almost identical to yours.
Thanks!
Hi Wayne.
It sounds like the last post you made and it possibly the video file type in use if the program is crashing using the nvidia card. Did you convert the files as previously suggested? iPhone files have always been problematic since they started to use a variable frame rate encoding method. This is just not a problem limited to VPX but I see a lot of similar complaints on other forums.
Variable frame rate video contains information about how to handle the file during playback including 'Hold this frame for X amount of frames',or 'play this section at XXX frames per second'. That causes problems for most video editing packages when the file needs to be cut or when frames need to be duplicated or dropped to keep the file ready for conversion to constant frame rate. Which frames need to be dropped without visible jumping of the moving image is needed when the frame rate increases for instance.
The problem is that the specific codec / wrapper altered by Apple and is not a shared standard. The program cannot read the files header correctly and can cause crashes when edited into portions. The files must be converted to a constant frame rate for the program to edit correctly. Also the iPhone records audio at 44.1kHz and video editors prefer handling audio at the video standard rate of 48kHz and will either have to be altered to the original file sample rate in the export settings or may cause a slightly longer render time if the audio sample rate is not altered when you also convert the video to CFR.
Some of the older iPhones had the ability to record at a constant frame rate as well and could be made in the settings. If that is still an option I would suggest using it for future recordings.
If the files have been converted then I am at a loss as to why the program would crash with using the nvidia card.
Ray.
Hi
Are you still using VPX 11?
Does the export freeze at the same point in the timeline?
Are there any error messages or entries in the crash log?
Did you install the Studio drivers for the RTX 3080 and are they up to date - current version is 472.47 (30.0.14.7247) ?
John EB
Forum Moderator
In my years of experience, MEP is a dog when it comes to encoding times. It consistently takes 5 times longer to do an MP4 than VideoRedo and Virtual Dub. Those two thrash my CPU but most of the time MEP just chugs along like a slowcoach.
Given Wayne is on VPX11, it would be interesting to see the difference in export time using VPX 13 with it's "Infusion" stuff, on what could only be described as an insane computer. I am extremely jealous! 😮
Hi Wayne.
It sounds like the last post you made and it possibly the video file type in use if the program is crashing using the nvidia card. Did you convert the files as previously suggested? iPhone files have always been problematic since they started to use a variable frame rate encoding method. This is just not a problem limited to VPX but I see a lot of similar complaints on other forums.
Variable frame rate video contains information about how to handle the file during playback including 'Hold this frame for X amount of frames',or 'play this section at XXX frames per second'. That causes problems for most video editing packages when the file needs to be cut or when frames need to be duplicated or dropped to keep the file ready for conversion to constant frame rate. Which frames need to be dropped without visible jumping of the moving image is needed when the frame rate increases for instance.
The problem is that the specific codec / wrapper altered by Apple and is not a shared standard. The program cannot read the files header correctly and can cause crashes when edited into portions. The files must be converted to a constant frame rate for the program to edit correctly. Also the iPhone records audio at 44.1kHz and video editors prefer handling audio at the video standard rate of 48kHz and will either have to be altered to the original file sample rate in the export settings or may cause a slightly longer render time if the audio sample rate is not altered when you also convert the video to CFR.
Some of the older iPhones had the ability to record at a constant frame rate as well and could be made in the settings. If that is still an option I would suggest using it for future recordings.
If the files have been converted then I am at a loss as to why the program would crash with using the nvidia card.
Ray.
Thank you very much, Ray.
Sadly I had a far from optimal experience (quality-wise and speed / workflow-wise) trying to convert the (VFR) MOVs from my iPhone 12, so I had to abandon that process. I also had a bad experience with HEVC (I could very clearly see the quality difference even on max quality settings) so I abandoned that workflow as well.
Yes, I have set the audio sample rate to 48kHz, and the iPhone audio is likely 44.1kHz. I set it that way because the music is 48k, but I'll try setting 44.1 on my next export to see if that helps, but I assume my mixed sample rates might be contributing to the slow export times. I'll see if I can download the music at 44.1.
I just realized that I have a single clip that I slowed down 50%, so I lied about not using any effects. :) I'll test with that clip at original speed and see if that helps.
I bought an iPhone 13 Pro today, as my 12 is struggling from sand and salt water. I assume I'll have all the same problems with VFR on the 13, is that right?
Thanks!
Hi
Are you still using VPX 11?
Does the export freeze at the same point in the timeline?
Are there any error messages or entries in the crash log?
Did you install the Studio drivers for the RTX 3080 and are they up to date - current version is 472.47 (30.0.14.7247) ?
John EB
Forum Moderator
Thanks John,
Yes, I think so. Version 17.0.3.68 (UDP3).
No, it is apparently random, sometimes freezing 15 minutes in, sometimes 5 hours in, even with the exact same timeline / clips / edits.
I had totally forgotten about the studio drivers and have been using the game ready drivers. (I mostly game on this PC and forget to switch when I'm editing.) I will switch to those immediately and try again.
Thank you!
In my years of experience, MEP is a dog when it comes to encoding times. It consistently takes 5 times longer to do an MP4 than VideoRedo and Virtual Dub. Those two thrash my CPU but most of the time MEP just chugs along like a slowcoach.
Given Wayne is on VPX11, it would be interesting to see the difference in export time using VPX 13 with it's "Infusion" stuff, on what could only be described as an insane computer. I am extremely jealous! 😮
Thanks! What is MEP? <sheepish grin>
Thanks, but until I figure out / my issues with VPX11, I am unlikely to upgrade. ;)
@Wayne-McIlvaine Movie Edit Pro, younger brother to VPX. 😉 Mostly the same guts, less bell and whistles.
Hi
. . . . my issues with VPX11, I am unlikely to upgrade . . . .
That triggered another line of thought 😁 - check the version of DirectX you have installed.
Open a command prompt - Windows key + R, type in dxdiag and OK.
You should have DirectX 12 installed.
John EB
@Wayne-McIlvaine @AAProds @johnebaker
Hi Wayne.
Sorry for the late reply but I've been out.
I think every upgrade on a phone normally means upgraded software and codecs as well as the hardware so yes it may be worse or the same. The files will probably not be easier to decode as Apple refines their codecs.
But that is generally true of all newer methods of encoding video. It's not just iPhones that cause problems, some newer mirrorless and DSLR camera codecs are also causing problems.
All the latest drivers and system builds are always in my signature. They are seldom more than a few days out of date. If you have added a slow mo effect to a variable frame rate file that is not going to help much.
It may be an idea to put a clip from your phone into Dropbox or Google drive to share so we could perhaps try to simulate the problem. Copy the file to roughly the same length as your project and see what rendering times are like or if we suffer freezes etc. I still think conversion of the files is the way to go.
While AAProds is correct about the encoding times compared to programs like video redo, they are basic cut and paste jobs rather than full editors with bells and whistles. I don't even know if they handle 4K or not or what the performance would be like with such files.
Your video card is light years ahead of mine but you lack an Inboard Intel GPU so I'm curious about how much slower or faster that difference makes.
Ray.
Exports without GPU.
https://au.pcmag.com/video-editing/51015/magix-movie-edit-pro-premium
Sorry for the slow response: I had to put this project down for a few days, but I think I've made some progress, and now I have a new question that might need a separate post, but I thought I'd share it here as well.
After trying everything recommended above, and seeing little to no improvement in my export times, I realized I had accidentally created my project as 4096x2160, and the content is all 3840x2160. I followed some tips on how to copy all my video and music objects from the 4096 project to a new 3840 project (by importing them both into one new project), and the export times were significantly improved, BUT... the copy / paste did not work properly, and many of the objects were no longer aligned properly on the timeline (requiring a ton of edits I'd prefer not to have to redo), and even worse, the exported video had unintended black bars on the side due to the rez differences:
So I have two questions:
1) can I just change the original project settings to 3840x2160, instead of having to do this copy (and how do I do this?), or do I have to create a new project and copy / redo edits?
2) If I'm stuck creating a new project and do a copy / paste, how can I avoid the black sidebars, and how to I ensure the objects paste 100% correctly onto the new timeline?
Thanks!
Sorry, I realized I misspoke on my previous post. If I recall correctly, I think a) the black sidebars came from just trying to export the original 4096x2160 timeline to a 3840x2160 video (which does not improve export times, but did allow me to avoid having to re-edit the objects to fit the new timeline properly)... and b) the export speed improvement came from copying / pasting the objects from the 4096 timeline into a 3840 timeline (but resulted in improperly pasted objects, requiring a ton of re-edits).
So what I am hoping is that I can just change the original projects settings and have the best of both worlds (no sidebars and no re-edits), or figure out a way to properly copy / paste so the timings are 100% perfect from the source timeline to the target timeline.
Thanks!
Sorry for the slow response: I had to put this project down for a few days, but I think I've made some progress, and now I have a new question that might need a separate post, but I thought I'd share it here as well.
After trying everything recommended above, and seeing little to no improvement in my export times, I realized I had accidentally created my project as 4096x2160, and the content is all 3840x2160. I followed some tips on how to copy all my video and music objects from the 4096 project to a new 3840 project (by importing them both into one new project), and the export times were significantly improved, BUT... the copy / paste did not work properly, and many of the objects were no longer aligned properly on the timeline (requiring a ton of edits I'd prefer not to have to redo), and even worse, the exported video had unintended black bars on the side due to the rez differences:
So I have two questions:
1) can I just change the original project settings to 3840x2160, instead of having to do this copy (and how do I do this?), or do I have to create a new project and copy / redo edits?
2) If I'm stuck creating a new project and do a copy / paste, how can I avoid the black sidebars, and how to I ensure the objects paste 100% correctly onto the new timeline?
Thanks!
can I just change the original project settings to 3840x2160, instead of having to do this copy (and how do I do this?), or do I have to create a new project and copy / redo edits?
You can certainly change the movie settings whenever you like (and you can have different settings for each movie, so it's not just one "project" setting). The only potential glitch will be if you change the frame rate; that may affect the layout of your objects.
can I just change the original project settings to 3840x2160, instead of having to do this copy (and how do I do this?), or do I have to create a new project and copy / redo edits?
You can certainly change the movie settings whenever you like (and you can have different settings for each movie, so it's not just one "project" setting). The only potential glitch will be if you change the frame rate; that may affect the layout of your objects.
Thanks, but how do I do that? I cannot find such an option to change the settings for an existing project. And will doing that completely change the project to the new resolution, or will there be some remnants of the old resolution?
Thanks!
@Wayne-McIlvaine File>Settings>Movie...
In your case, choose UHD from the video Settings dropdown, then Ultra HDTV 16:9. This is for MEP. I assume VPX is similar:
No remnants, you will probably get a popup to adjust the Preview window to the changed settings, click "Adjust". You may see the aspect ratio of the monitor screen (the jet black area) change slightly from 4096x2160 to 3840x2160.
In the context of aspect ratios, forget the term "project settings". These are movie settings and can be different for different movies in the same project.
@Wayne-McIlvaine File>Settings>Movie...
In your case, choose UHD from the video Settings dropdown, then Ultra HDTV 16:9. This is for MEP. I assume VPX is similar:
No remnants, you will probably get a popup to adjust the Preview window to the changed settings, click "Adjust". You may see the aspect ratio of the monitor screen (the jet black area) change slightly from 4096x2160 to 3840x2160.
In the context of aspect ratios, forget the term "project settings". These are movie settings and can be different for different movies in the same project.
Thanks! No wonder I couldn't find the project settings!
The swap worked, and I didn't have to do any edits, but now I'm stuck in a crashing loop. I have attempted to export this movie to MP4 at Best quality 7 times now and it has crashed every single time about 3-4 hours into the export. As a test, I did a "Balanced" export and it worked, and finished in about 2 hours.
I have really come to the end of my rope with the stability of VPX, and have wasted literally days (not to mention a ton of electricity) trying to render / export simple movies. I know you all say all NLEs will struggle with VFR video, but I tried with just clips from my DJI Mavic and VPX crashes exporting that video as well. This is without hardware acceleration, no special effects, and standard settings.
So what are my options now if I don't want to keep banging my head against a wall? Is there direct support for the version of VPX I have, where they could look at crash dumps or something? If not, is there any other option for me? Premiere Pro seems overly expensive for what I need, and I don't have a Mac for Final Cut. In the end, any NLE that is more stable is worth it to me.
Thanks!
Hi Wayne.
Which DJI Mavic drone do you have? Some of them can record in Apple ProRes 422 HQ which is also a problematic file format. The only person I know that successfully edits that footage is using Grass Valley Edius Pro using an Apple M1 Pro.
The only thing I can think of that I haven't asked is what CPU heat sink are you using? While the computer should not crash it may be throttling down due to excessive heat build up and I'm not sure if that will effect the program. Most of us here that I know of have very good CPU heat sinks. My CPU rarely ever gets above 47℃.
Then again I never overclock my system which can cause additional problems.
Hi Wayne.
Which DJI Mavic drone do you have? Some of them can record in Apple ProRes 422 HQ which is also a problematic file format. The only person I know that successfully edits that footage is using Grass Valley Edius Pro using an Apple M1 Pro.
The only thing I can think of that I haven't asked is what CPU heat sink are you using? While the computer should not crash it may be throttling down due to excessive heat build up and I'm not sure if that will effect the program. Most of us here that I know of have very good CPU heat sinks. My CPU rarely ever gets above 47℃.
Then again I never overclock my system which can cause additional problems.
Thanks. I have a Mavic Mini 2, and it is not using ProRes.
This is my CPU cooler / fan (a DarkRock Pro 4): https://www.bequiet.com/en/cpucooler/1378
I've been watching my CPU and GPU temps and they are all well within expected ranges while under heavy load, including export.
After 2 more hangs at 3+ hours of export, I broke down and upgraded to VPX 13. Not only did the 15 minute video render / export in under 5 minutes, but I had no hang. So while I would have loved to save the $149, it was better than driving myself crazy. 😟
Thanks all!
Hi Wayne.
That's encouraging. It just goes to show how the program is updated for newer hardware which could explain it.
I don't think the RTX 3080 was released when your previous version of VPX was released.
Glad it is running much better for you. I for one have learned something new from all of this.
Ray.
FYI, MAGIX recommends the Nvidia Game Ready Drivers, NOT the Studio Drivers. Here is their response to my support ticket about this issue:
Thank you for your message. The two main problems I havenoticed so far are:
- you are using an older version of the program that can't use your Nvidia graphics card for the export.
- you are using the Nvidia Studio driver. WE alwys recommend the Game-Ready driver as we have tested our programs with these drivers and we could solve many export problems by using the Game-Ready-Driver.
https://www.nvidia.com/de-de/drivers/results/184003/
Please laso make sure you have downloaded and installed th elatest Intel graphics driver as it is used for the export.
https://www.intel.com/content/www/us/en/download-center/home.html
Let me know if the problem persists.
Hi Wayne.
Thank you for this information as we have not seen this published anywhere to my knowledge.
Did it in fact resolve the problem?
Ray.
@Wayne-McIlvaine @CubeAce @johnebaker @AAProds
Hi
WE alwys recommend the Game-Ready driver as we have tested our programs with these drivers and we could solve many export problems by using the Game-Ready-Driver.
Interesting revelation considering the Nvidia drivers get updated every couple of weeks....so should we just revert to the drivers that were current when the program version was tested / released......? 😆
Anyway Wayne you said you were on the Game Ready drivers and tried both and they did not fix the problem with VPX11.
Further - your VPX 11 would not have been using the Nvidia card for HWA during export unless you were exporting to HEVC, and your dramatic increase in render speed would have been due to the NVENC chip on the Geforce card doing the bulk of the encoding via the new Infusion Engine 3 in VPX13 when you upgraded.
I presume your Intel Integrated GPU was active and updated, and that HWA was selected for export in at least some of your original tests?
Peter