Vegas Pro 15: MAGIX AVC/AAC codec not supporting 60 fps

Back to post

Comments

Graviphoton wrote on 1/29/2018, 6:22 AM

I am not an expert but there are strong indications that NVENC should work with much wider list of frame rates than those offered in Magix AVC codec:

  1. NVidia's GeForce Experience can record video content to 60 FPS on-the-fly.
  2. Open Broadcast Software using NVENC can record 60 FPS, 120 FPS, 240 FPS or even higher (according to https://forums.geforce.com/default/topic/998413/shadowplay-120-fps-recording-support-obs-already-does-it-with-nvenc-h265-/).
  3. NVENC Encoder API defines frame rate as a fraction of two whole numbers Frame rate = frameRateNum / frameRateDen. I didn't find any limitiations on frameRateNum's or frameRateDen's values mentioned.
ivan-p wrote on 2/7/2018, 9:51 AM

NVENC via FFmpeg allows for virtually any frame rate, so its a bug in Vegas 15 261 --- I tested QSV only via Handbrake and it too allows custom frame rates.

I've tested NVENC with OBS and can use any custom frame rate.

With 261 CPU encoding allows for any frame rate, but its just too slow for my files on a Ryzen 5 1600X (6 core)

Otherwise I'm very happy with Vegas 15

HologramSSBM wrote on 2/14/2018, 11:12 AM

I am also experiencing this issue. This is the English version, Vegas 15 build 261. Inputting a custom value into the Frame Rate field just has it revert back to 23.976.

This only happens when i have the Encode mode as NVENC. If encode mode is set to Mainconcept AVC, I am able to put in a custom frame rate.

All my footage is at 60fps. The highest option NVENC allows is 59.94fps.

What would be the main downside of rendering the 60fps footage at 59.94fps? Will I drop a frame ~ every 16 seconds? How will audio be effected? I rendered a test video and couldn't notice anything bad about it. I have the Project Properties set to 60fps, with Re-sample Disabled.

 

 

 

NickHope wrote on 2/14/2018, 11:59 PM
All my footage is at 60fps. The highest option NVENC allows is 59.94fps.

What would be the main downside of rendering the 60fps footage at 59.94fps? Will I drop a frame ~ every 16 seconds? How will audio be effected? I rendered a test video and couldn't notice anything bad about it. I have the Project Properties set to 60fps, with Re-sample Disabled.

@HologramSSBM Yes, shouldn't really be a problem but having resample disabled is critical.

Graviphoton wrote on 2/28/2018, 3:29 AM

Situation in VEGAS Pro 15 Update 3 (build 311) is still unchanged.

3mix wrote on 3/10/2018, 6:29 PM

I'm on build 177, still not able to input a custom framerate on the same template. Have tried "60", "60.0", "60,0" etc. and they all get changed to 12 fps automatically.

There is untill now only one build 177 and that one I use.
Are you sure to use the MAINCONCEPT AVC/ACC codec?
That one is not available by default, you have to allow it in Options/Preferences/Internal
You can see Internal by selecting Preferences with hold Shift button.

this is how you have to enable this?why?why would this not be a default option?just weird!..and thank you for showing us

 

MaximusPanin wrote on 3/10/2018, 9:28 PM

Situation in VEGAS Pro 15 Update 3 (build 311) is still unchanged.

Graviphoton, try it build 321 

Graviphoton wrote on 3/11/2018, 1:22 AM

Context of my post is "using NVENC" = fast GPU accelerated mode, not original slow Mainconcept which I am fully aware is now functional. Although your screenshot shows only Mainconcept I wil try it.

Thanks for notice.

Graviphoton wrote on 3/11/2018, 5:32 AM

@MaximusPanin Build 321 is the same no 60 fps support for NVENC.

phil-d wrote on 3/11/2018, 9:16 AM

Hi

Seems it's just another bug with Vegas. This is a screen shot from all the supported frame rates using Intel QuickSync in TMPGenc Video Mastering software (which also works with 10 bit HEVC, unlike Vegas!)

There is no reason why any encoder is restricted to certain frame rates, unless it is a real-time encoder, which under discussion these aren't.

Regards

Phil

Graviphoton wrote on 9/5/2018, 2:05 AM

No progress in Vegas Pro 16.

howlyeye wrote on 9/9/2018, 1:07 PM

I seem to be experiencing the same symptoms. I noticed in Nick Hope's thread on Known Problems that this was removed from the list as a result from a fix in build 261? I think he was referring to regular MainConcept, not the NVENC. I can't seem to find a solution to this problem either. I'm also using footage from ShadowPlay.

NickHope wrote on 9/9/2018, 8:50 PM

I seem to be experiencing the same symptoms. I noticed in Nick Hope's thread on Known Problems that this was removed from the list as a result from a fix in build 261? I think he was referring to regular MainConcept, not the NVENC...

I was.

  1. Has anyone made a support request about the problem with NVENC frame rates? If so, what was the reply?
  2. Which exact frame rates is NVENC encoding missing, that MainConcept encoding allows?
  3. How about VCE encoding? Same issue?
howlyeye wrote on 9/9/2018, 9:26 PM

I just made a support request for this problem. I just checked and I was able to create templates for the MainConcept AVC/AAC format that used 30.0000 and 60.0000 framerate no problem.

However, I was unable to create a custom framerate at all while using the MAGIX AVC or HEVC NVENC options.

I tried both 30 and 60 as framerates, and even arbitrary 28 and 42 and tried to save these templates. All of my choices reverted to the 23.976 (IVTC Film) preset.

howlyeye wrote on 9/10/2018, 2:13 PM

The response I got from my support ticket was as follows:

Thank you for your message. Nvidia, as well as any other hardware accelerated render settings, have a different framerate limit then the software itself. The software is programmed so if an invalid value is entered into the framerate for these codecs (for example 60) it defaults to the default value. 

If you need to use the Nvidia format the closes to 60 will be the max 59.94. If you can use just a standard AVC/HEVC format it will allow you to have the custom 60.

A little unfortunate to hear that it's something we seemingly just have to deal with.

Graviphoton wrote on 8/22/2019, 5:43 AM

Problem with 60 fps using NVENC is finally solved in Vegas Pro 17.

grokMan wrote on 8/28/2019, 6:46 PM

I was just trying this out with AMD HEVC (AMD VCE) and the problem of not being able to input discrete (integer) custom frame rates remains for this encoder. Seems strange it would be fixed for the Nvidia one but not the AMD one. Is this in the works?

vkmast wrote on 8/28/2019, 6:54 PM

@grokMan please read.

grokMan wrote on 8/28/2019, 10:43 PM

OK right on & thanks @vkmast for sharing the link. I was one of those like he mentioned that had switched to an AMD board specifically b/c there was no Nvidia support "back in the day". But its not a total loss because I still get acceleration in edit & render, just not for H265 (yet, presumably). Good to know its in the works. However, its not totally clear to me if the FPS issue will be resolved at the same time as the underlying encoder work. For that reason I opened a ticket to ask that they include the same manual-FPS-setting repairs for AMD as they ultimately did for NVidia - when the AMD HEVC feature work rolls out.