Video For Windows crash

3d87c4 wrote on 9/21/2018, 4:52 PM

I make 4K 3D 360 VR videos and have been using x264VFW to render 3840x1920 top/bottom full 3D MP4 files (3840x3840 final file size) via presets I created in the Video For Windows render option. This has worked fine in Sony V13 and Magix V14 and V15.

For some reason x264VFW is only accessible as a pull down option in the NTSC DV option, so I highlight it and select Customize Template to get to it. This causes V16 to crash!!!

Is there some other way to access x264VFW?

Is there another render option that will allow me to create 4K 3D top/bottom videos?

Up 'til now I did all of my editing in V13 so my files could be read, and rendered, by the newer versions. For my latest video, I thought I'd try out V16's VR capabilities---not much, IMHO---so rendering with V15 or V13 isn't an option.

I punted by rendering the left and right clips separately, using the Intermediate Render option, and using FFMPEG to combine them into a top/bottom format.

Is there a better way to do this?

Comments

Red Prince wrote on 9/21/2018, 7:44 PM

Oh, for some reason after seeing the thread title, I was expecting someone to ask how to make a video about a Windows crash (English is my fifth language, so I interpreted it wrong). And I was going to recommend hooking up an external recorder to the HDMI output of the computer. :)

3d87c4 wrote on 9/21/2018, 8:54 PM

LOL

At least you replied...my threads tend to fade away unresolved...

Red Prince wrote on 9/21/2018, 11:08 PM

Well, I hope someone who knows the answer to your question will reply soon.

j-v wrote on 9/22/2018, 4:28 AM

Did you install the 32 or the 64 bits version of that codec or maybe both?
With the 64 bits I have no problems to render in Vegas Pro 16.
Take a look:

3d87c4 wrote on 9/22/2018, 6:11 PM

I'm not sure...so...

I deleted it, via the appropriate windows control panel tool, and re-installed just the 64bit version (labeled x64).

Here's where things drift into voodoo science...

I fired up V16, opened this weeks project (Dive 498) and attempted to render via video for windows & Vegas became unresponsive when I clicked on Customize Properties. Didn't crash outright, but...

I then fired up SV13 and opened a previous 360VR project (Dive 497) and was able to Customize Properties and access the x264VFW menus. I exited without actually rendering anything.

Turning V16 back on, I opened Dive 497 and everything seemed to be working. I could Customize Properties and access the x264VFW menus. I closed that render session, without actually rendering.

I then opened Dive 498 (the one that was crashing), checked the project settings to be sure it was set to 3D top/bottom full (not 360 output), and WAS able to start a render using my old x264VFW preset.

I have two thoughts:

Accessing the older project set, or reset, something in V16 that allowed it to work & my problem is solved.

or

In the course of editing Dive 498 I went back and forth between enabling 360 output, and enabling 3D top/bottom full. My fear is that going back and forth between 360 and 3D is the reason for the crashes, and the problem will recur in future 3D/360 projects.

3d87c4 wrote on 9/24/2018, 3:26 PM

The plot thickens...

The render mentioned above completed fine.

A few minutes ago I opened V16, loaded Dive 498.veg, and Video For Windows Customize Properties crashed Vegas!!!

Restarting V16 and loading the older file, Dive 497.veg, and everything's fine---I can use Customize Properties to set up a x264VFW render for both Dive 497.veg and Dive 498.veg.

Shutting down and restarting V16, loading Dive 498.veg, and Customize Properties causes V16 to go unresponsive.

So now I have a reproducible problem. What should I look for when comparing the projects, that might trigger this? Or should I try to figure out how to get Magix support?

3d87c4 wrote on 9/24/2018, 4:00 PM

I have a support ticket # and am waiting for a response.

Musicvid wrote on 9/26/2018, 2:39 AM

X264vfw is not suited for large files because compression is horrible without any redeeming qualities. Without b-frame support, it is really no better than mpeg compression. If you want clean lossless mpeg compression, xavc-I is your friend, but its it's big,too.

Video for Windows (AVI) carries a maximum 4GB maximum file size (2 GB if on a FAT partition).

X264vfw is third party software. I don't know how much interest Magix Support will be able to take. X264vfw is lossy compression; xavc-I is lossless

AVI can't produce vbr audio, except DivX codec comes with a hack.

3d87c4 wrote on 9/26/2018, 11:07 AM

The problem has nothing to do with x264VFW, as it occurs when selecting Customize Properties---before accessing x264VFW.

Can xavc-l render a 4K top/bottom full 3D video?

I'm open to any codec that can.