List of Problems MAGIX AVC/AAC including NV Encoder [Vegas Pro 15]

CrespoFTW wrote on 8/30/2017, 11:20 AM

Recently converted from Vegas Pro 14 to 15 and notice some problems

Before I switch, I rendered my latest youtube video using Mainconcept AVC/AAC on Pro 14 and then rendered on Pro 15 using the default cpu render. It actually took 2 minutes longer to render......strange but it get more odd

Vegas Pro 14: 18:52

Vegas Pro 15: 20:57

Once I rendered I check the sound quality of Pro 15 video and realize the sound was odd, like it sometime peaking and goes robot-ty. The Pro 14 video didn't do this at all and the render settings are the same.

 

Ok so I tried the NV Encoder, It's amazing...........but no matter what setting I set to it always end up being the same file size, half the bitrate I set it to and the audio is still messed. Now this is the biggest problem I got. Playback. Pro 14 runs smooth, I can skip through the video with no problem at all but now with vegas pro 15 if I skip through the video it freeze's and sometime take 10 or more seconds to respond.

I'm loving Vegas Pro 15 design but I'm sticking with Vegas Pro 14 until this get iron out a little. I wanted to help by showing all the issues I had and hopefully someone from MAGIX will read this.

 

 

Ok the technical stuff

OS: Windows 7

CPU: I7-5930K

Ram: 16GB

GPU: GTX 1080 Strix

 

Render Settings

Mainconcept AVC/AAC

1920x1080

Profile: High

Frame rate: 59.94

Constant Bitrate: 20,000,000

Sample rate: 48,000

Bitrate: 192,000

 

I can upload the videos but I not sure if people want to watch a 7 mins video of a random guy rambling

 

Comments

NickHope wrote on 8/30/2017, 11:33 AM

https://www.vegascreativesoftware.info/us/forum/new-avc-issues-in-vp15-try-disabling-so4compoundplug-dll--108345/

CrespoFTW wrote on 8/30/2017, 11:44 AM

I'm giving this a try

CrespoFTW wrote on 8/30/2017, 1:20 PM

Playback is fixed but audio is still peaking. Audio is fine during editing but the rendered video is just off

NickHope wrote on 8/30/2017, 2:53 PM

Playback is fixed but audio is still peaking. Audio is fine during editing but the rendered video is just off

If you think that is due to the MAGIX AVC/AAC encoder then you can still enable the MainConcept AVC encoder in VP15.

  1. Hold the SHIFT key while clicking Options > Preferences
  2. Click "Internal" tab
  3. Type "Main" in the field at the bottom
  4. Set "Enable MainConcept AVC/AAC Render plugin" to TRUE
  5. If you want GPU rendering and have an old supported GPU, on the General tab check "Allow legacy GPU rendering"


Please compare the MAGIX AVC/AAC render with the MainConcept AVC with as like-for-like settings as you can. If you think there's a difference with the rendered audio (i.e. a bug in the new encoder), please let us know.

CrespoFTW wrote on 8/30/2017, 4:15 PM

Just finished rendering using Vegas Pro 15 with Mainconcept AVC/AAC and yep the audio actually turn out fine. Render time took 20 mins

 

MAGIX AVC/AAC have an issue with audio nearing peak or randomly going static........it's a bug

 

But thanks to your solution I can use Vegas Pro 15 while using the original AVC/AAC format. I hope in time this will fixed, so I can use NV Encoder without any audio issues..........THE DREAM :')

NickHope wrote on 8/30/2017, 10:41 PM

Just finished rendering using Vegas Pro 15 with Mainconcept AVC/AAC and yep the audio actually turn out fine. Render time took 20 mins

MAGIX AVC/AAC have an issue with audio nearing peak or randomly going static........it's a bug

But thanks to your solution I can use Vegas Pro 15 while using the original AVC/AAC format. I hope in time this will fixed, so I can use NV Encoder without any audio issues..........THE DREAM :')

Thanks for the feedback. Could you please post your video and audio render settings so others can test this to verify if there's a bug and get it fixed? Screengrabs would be ideal if you made any custom settings. Also it would be great if you could post a link a short sample of this media that displays this bug when it's rendered.

CrespoFTW wrote on 8/31/2017, 3:07 PM

After a bit of research and constant rendering I found a solution. Rendering at a higher audio bitrate 256,000 fixes this problem but I learnt what the real issue of MAGIX AVC/AAC

 

The finish rendered video properties is never the same as what it is set to. I rendered 20,000,000 bitrate but the project end up being 15-16kbps. This is why the total file size is lower then what the program predict.......the file is actually meant to be 900MB not 750MB.

 

Where the sound problem come from? easy the audio bitrate is also suffering from this same issue instead of the audio rendering at 192kbps, in properties the video audio is running at 189kbps........audio may sound fine but in certain spots it shows it true colours.

 

So rendering at a higher audio bitrate means it fixes the issues but it still suffer from the same issues but it harder to tell as the bitrate goes up

 

I really hope this helped

thore-malmin wrote on 9/11/2017, 2:06 PM

how to set a custom fps? vegas pro 15 won't let me😭

Former user wrote on 9/11/2017, 8:09 PM

"I can skip through the video ... "

I mentioned the slow seek time in another post ... https://www.vegascreativesoftware.info/us/forum/video-file-seek-very-slow-on-selected-hw-rendered-nvenc-files--108569/

I'm guessing that maybe some of this is due to the possibility that some settings that give slow seek are actually for streaming? Anyway 3 of the 6 nvenc possible settings don't give this problem.

I found also that my 720x576 (or 640x480) settings always gave around 11mbps no matter what data rate I set.

But if you're using higher resolution than sd then it follows the data rate you set some of the time.

I suspect that these limits are built in to the hardware nvenc chip?

If thats true then Magix shouldn't be allowing users to enter values in the NV templates that arent possible. If there are only discrete data rate values available for different resolutions then discrete values in a "list" should be presented instead. If its true there are only some discrete values available, they may be different for different cards!