Crashing in video proX14

CubeAce wrote on 12/11/2023, 3:03 PM

Hi and welcome to the user to user forums.

I too am running VPX 14 and you are running the last updated version.

First make sure you have more than 10GBs of free space on your C: drive for the program to produce the temporary files it needs to use while rendering. Next check with the manufacturers websites (Not Windows) that you are running the latest graphics drivers for your graphics card if that does not work.

I take it you have not had trouble with previous projects?

If you are crashing the program does it generate a warning? If so what does it say?

Ray.

Stanislav-Zakharov wrote on 12/11/2023, 4:07 PM

Hi Ray. Yes I have more than 10Gbs of free space. I have AMD Ryzen 5 5600U with Radeon Graphics

Stanislav-Zakharov wrote on 12/11/2023, 4:07 PM

and still have a problem

CubeAce wrote on 12/11/2023, 4:28 PM

@Stanislav-Zakharov

In the program under file / Settings / Program, and using the Device options tab, try setting all the settings for Import, Processing, and Export to CPU. It may take a while for the project to render but should not crash.

If it still crashes then in the same tab change the standard renderer to Alternative mode 2. but not before trying the other bit first.

Ray.

CubeAce wrote on 12/11/2023, 4:45 PM

@Stanislav-Zakharov

Where are the projects video files stored? Which drive? You have a laptop yes?

What are the video files from? A camera, a phone, or screen recording?

Ray.

Stanislav-Zakharov wrote on 12/11/2023, 6:21 PM

Hi Ray, just a quick question. When all are changed to CPU, does the renderer need to standard? All project video files are stored in a local C laptop drive. But all the files I gave dragged and dropped from the external hard drive. Regarding the type of files, drone, GoPro, phone. Regards Stan.

CubeAce wrote on 12/11/2023, 6:39 PM

@Stanislav-Zakharov

Hi.

No, but some Go-Pro files can be difficult to handle if they have variable frame rates. HEVC encoded files can be too much for a lower specified machine to handle.

Projects should ideally be made up from videos all containing the same frame rate and resolution or the program cannot generate extra frames or take frames away to produce a constant frame rate render.

To find out if your files have variable frame rates you would need to download MediaInfo and take a look at the video data from the text view. If the frame rate varies by more than a few frames per second you may have to use a program like HandBrake to convert them to a constant frame rate first.

The Go-Pro file problem with video editors is well documented on the Go-Pro website.

If in doubt post the mediainfo results here for others to look at.

Ray.

Stanislav-Zakharov wrote on 12/11/2023, 7:07 PM

Thanks mate.

Stanislav-Zakharov wrote on 12/12/2023, 5:11 AM

Ray, just a quick Q for you. I have 1600 number of used objects. How can I sort it out? I probably need a different machine, laptop; my laptop is not doing good.

johnebaker wrote on 12/12/2023, 6:19 AM

@Stanislav-Zakharov

Hi

. . . . I probably need a different machine, laptop; my laptop is not doing good . . . .

I would agree with you on this.

If you decide to upgrade to a better PC then, I Personally, would avoid using any AMD based system for video editing.

A system with an Intel 10th generation CPU, i7-10xxx or better/newer with integrated graphics, and, either an Intel ARC or NVidia RTX series GPU will work better with VPX14, and 15.

If you want to go with a laptop then see my Signature for what I use. The ability to use both the Intel UHD 630 GPU and the RTX 2060 in 'hybrid mode' is good for performance - many other laptop manufacturesers do not offer a 'hybrid, mode.

HTH

John EB

CubeAce wrote on 12/12/2023, 6:48 AM

@Stanislav-Zakharov

I would have said the same as @johnebaker regarding machine specifications. While AMD can work the components lack some of the hardware acceleration benefits that Intel and nvidia products have that help with video encode and decoding.

Whenever you look as the specifications of any software regarding what is needed take the minimum specs as meaning all of the components listed for the program to run. Start to mix things up by adding effects and file types and the specification also tends to need to be increased by quite a margin if you expect trouble free performance.

Yes often editing can be done on lower end machines but the experience is often less than desirable if not downright annoying.

For VPX 14 the minimum specs should be but preferably exceeded.

But personally I would opt for at least 32 GB of ram along with John's other suggestions as well as at least two internal drives, more if possible.

Ray.

browj2 wrote on 12/12/2023, 7:25 AM

@Stanislav-Zakharov

Hi,

Regarding the type of files, drone, GoPro, phone.

I suspect that you have at least one file in there that VPX does not like, probably one with variable frame rate.

I suggest that you check your files using MediaInfo. Start with phone files.

If you can identify where, approximately, VPX crashes, then you can try the files around that zone in another project to see if they cause a problem there.

Also, open the Microsoft Task Manager and watch your hard drive that has the files to see if anything strange happens during playback or export. I have files that send my hard drive to 100% for a few minutes, before being able to continue. I try to identify any files that cause that, run them through Handbrake, and replace the original with the same filename before reopening VPX. Of course, I keep the original elsewhere.

Failing that, check for any effects, especially transitions that use a video overlay (not your video).

John CB