HEVC Renderer Custom Frame Size Miscalculation [BUG]

AVsupport wrote on 10/12/2019, 10:38 PM

As I am rendering out an Instagram feed project h1350 x w1080,

When I am choosing MAGIX HEVC (nvenc) with custom frame size option, the resulting file is 1376x1088.

Needless to say it gets rejected when tried to upload to instagram feed because of the wrong frame size.

This doesn't happen with MAGIX AVC (nvenc)

Comments

NickHope wrote on 10/13/2019, 12:33 AM

1350 is only modulus 2. Not very helpful of Instagram to specify that resolution. Encoding to a higher modulus is more efficient and common.

It looks like HEVC rendering is forcing a higher modulus than 2. 1376x1088 is modulus 32. It might be forcing a lower modulus than that (4, 8 or 16), with 1376x1088 being the first match that is near enough the same aspect ratio as 1350x1080.

Will it render 1348x1080 (mod 4) or 1352x1080 (mod 8)?

There's a slightly related issue here wherein Intel 10-bit HEVC renders 1920x1080 to 1920x1088 (which implies that mod 16 was being forced).

AVsupport wrote on 10/13/2019, 1:17 AM

Goes back to VP14! Is this how old this is..

Will it render 1348x1080 (mod 4) or 1352x1080 (mod 8)?

No. It doesn't. resulting renders are both 1088x1376. (mind you I didn't save the render preset, just changed numbers)

So I guess wisdom is, forget HEVC for Instagram, unless you're doing traditional square or horizontal?

Sylk wrote on 10/13/2019, 4:22 AM

There's no problem from Vegas. There's a problem from Windows!

Windows File Properties shows 1088x1376, while MediaInfo shows 1080x1350. Same with import, Vegas properly shows 1080x1350.

So, NO BUG. Just a Windows File Properties mistake with HEVC sizes. +8 or +16 pixels.

(1280x720 looks 1280x736, 1920x1080 looks 1920x1088, 3840x2160 looks 3840x2176)

So I guess wisdom is, forget ...

... Windows File Properties to check the real media infos! Use MediaInfo or MPC-HC Properties.

AVsupport wrote on 10/13/2019, 11:20 PM

I guess some of the problem / answer is actually, as it turns out, I believe neither Instagram nor Facebook (who owns instagram) does support HEVC at this stage. still interesting though.. let the finger pointing continue.. ;-)

Sylk wrote on 10/14/2019, 12:27 AM

Have you tried to upload a standard size, like 1280x720 (width x height)?

Sylk wrote on 10/17/2019, 11:34 AM

@AVsupport problem solved or not?

AVsupport wrote on 10/17/2019, 7:32 PM

anyway, moving on..

Sylk wrote on 10/18/2019, 2:10 AM

Anyway, this https://www.vegascreativesoftware.info/us/forum/hevc-renderer-custom-frame-size-miscalculation-bug--117457/#ca732548 solves the title subject, so please check it as solution to close this thread.

AVsupport wrote on 10/18/2019, 2:19 AM

well I'm not sure if I can do that dear @Sylk since it's not exactly clear if VP renders actually do create an issue whereas windows sees wrong data.. cannot prove either way. Yes I do see clip info inside VP being correct but that's beside the point.

Anyway, moving on.

Sylk wrote on 10/18/2019, 4:33 AM

since it's not exactly clear if VP renders actually do create an issue whereas windows sees wrong data.. cannot prove either way.

@AVsupport Easy to check that. Try to create an 1920x1080 HEVC video from another software, like i did from bandicam, and you'll see that Windows shows wrong size. The same as a Vegas rendered video. For some reason a video 2560x1440 shows right, but not the other sizes.

For me this proves that Windows 10 isn't fully HEVC-ready, not that Vegas makes bugged HEVC files.

Solved, as i said 😉

PS: And how to move on while you accuse Vegas of bugs that are not his fault?