VP14 Build 244 - No render MainConcept mp4 possible

peter-s wrote on 3/31/2017, 3:25 PM

Hi,

yesterday I updated without a problem but I didn´t render a test. Now I finished editing, its no longer possible to render to any MainConcept mp4 in any resolution. Sony MP4 would be possible. After deinstalling 244 and reinstalling 211, its working again.

Also I think 244 is doing not good with Mercalli. I had problems stabilizing a 50P clip in a 25P project.
Ok, it should be the same, but after doing it, I always had this Mercalli Overlay in the Preview window. I only could get rid of it by deleting the clip from the project and re-adding it.

I will stay with 211 until a new release.

Peter

Comments

Cornico wrote on 3/31/2017, 4:11 PM

its no longer possible to render to any MainConcept mp4 in any resolution. Sony MP4 would be possible

No problem here with all kind of resolutions and framerates, default and customized.

Edit.
Total no problems on desktop.
On laptop only customized MC settings from other versions gives this error

 

D7K wrote on 3/31/2017, 7:03 PM

Just did a MC 4K -> 1080P and changed data rate and rendered fine on desktop.

peter-s wrote on 4/1/2017, 6:21 AM

As i just found out, I´m not the only one. Using Win 8.1 64bit
Maybe this might be a reason?

Cornico wrote on 4/1/2017, 7:31 AM

I don't think so.
Windows 10 pro uptodate here and its only with customized Mainconcept AVC templates from a former Vegas version.

Look

peter-s wrote on 4/2/2017, 5:43 AM

Thanks for your input. I also have customized templates, but they are converted/imported from 12->13->14.
I first will finish a project render and then reinstall the update an create a few new templates. Maybe then this might be a solution.

Cornico wrote on 4/2/2017, 7:32 AM

It is the solution. Templates that are/were customized in the latest version 244 render fine.

Peter_P wrote on 4/2/2017, 8:57 AM

I have a similar problem with the HEVC templates. Those, that I adjusted in B211 only show blank fields. If I take one of the B244 templates f.e. with 23.97 fps and change this to the required 29.97fps it will immediately be cleared when I call it up again.

Any hint, how I can render HEVC with 29.97 fps?

Peter_P wrote on 4/2/2017, 9:05 AM

Easy solution. I had to quit Vp14 and restart again. Now I cout set up a 29.97fps template.

Cornico wrote on 4/2/2017, 9:14 AM

Peter, that one I have build-in. I see it with no Filters on

Edit: I see you managed it. 👍

RealityStudio wrote on 4/2/2017, 12:04 PM

I just had this happen to me as well, but found out the reason was that build 244 wiped out all my Main Concept custom render presets. They were all still there but when I went to look at their settings, all the video settings were empty. Oddly my Sony AVC custom presets were untouched, it was just my Main Concept custom presets that it totally wiped. Had to remake my two custom presets, exit and relaunch the app and now I can render fine again.

Jam_One wrote on 4/2/2017, 12:56 PM

1) Render Presets are interchangeable between Vegas Pro Versions. We know that for our custom presets were all there in VP14 from the very beginning.

2) Vegas Pro 11 & Pro 10 both read (still!) all custom Render Presets stored under MainConcept AAC/AVC cover.

*Sherlock Holmes mode ON* ==>> The code in VP14 sends the poor thing to read the presets in question from some improper place where they never could have existed. And may be this place is not the most proper one to save custom presets to either...

 

.

Last changed by Jam_One on 4/2/2017, 1:00 PM, changed a total of 2 times.

Win 7 Ultimate | Intel i7-4790K @ 4GHz | nVidia GTX 760 4GB * 2

SSD | 32 GB RAM | No Swap file | No Overclock | GPU-in-CPU OFF

t.A.T.u. F.o.R.e.V.e.R.!

 

NickHope wrote on 4/2/2017, 1:30 PM

...Oddly my Sony AVC custom presets were untouched, it was just my Main Concept custom presets that it totally wiped...

From the build 244 release notes:

  • "We've created a new 4K render template for MainConcept AVC/AAC file format and exposed a new 4K frame size preset to make it even easier to create 4K files"
     

I guess something got mucked up when that change was coded and so this is why it's specifically affecting MainConcept AVC/AAC.

But I did get a ProRes template affected, and I don't think there's been a change there.

peter-s wrote on 4/3/2017, 10:30 AM

The resolution is, doing screenshot of old settings in 211 and creating new render profiles in 244.
When you do not know the exact settings, just uninstall 244. Do a install of 211 and you get access again to the profiles.
Hoping a patch is bringing back all old profiles, well for future it would be nice to have a possibility to export/import all render settings.

NickHope wrote on 4/3/2017, 12:29 PM

The resolution is, doing screenshot of old settings in 211 and creating new render profiles in 244.

That's an effective workaround, but a true solution will be a new build that fixes the problem.

Build 211 installer is here if anyone needs it to roll back: http://dl04.magix.net/2016/VEGASPro14/update/VEGAS_Pro_14.0.0.211_update_Retail_x64.exe

RealityStudio wrote on 4/5/2017, 3:58 AM

The resolution is, doing screenshot of old settings in 211 and creating new render profiles in 244.
 

Yeah fortunately I've always kept current screenshots of my custom presets as a precaution, been doing that since version 4.0, so restoring them was quick and easy.

Chuzz wrote on 4/10/2017, 1:55 AM

Yep big problems render in v14 244, I need 4 k 5.1 renders that work TODAY, not next month or year.Why are half the templates BLANK? It's really messed up.😰

Actually I'm having a hard time finding many renders that work properly , at all. It's a big list with dead ends everywhere, unless I want SD or VCD, yeah VCD templates, they're useful. lol.😕

GJeffrey wrote on 4/10/2017, 2:27 AM

Yep big problems render in v14 244, I need 4 k 5.1 renders that work TODAY, not next month or year.Why are half the templates BLANK? It's really messed up.😰

As far as I know, Mainconcept doesn't allow 5.1 audio, only stereo.

Chuzz wrote on 4/10/2017, 8:11 AM

Hey thanks for the reply! So are you telling me that Vegas will not render any 4k 5.1 file? That sounds absurd to me, obviously 4k 5.1 files exist, what format do I use and does Vegas support it?. I never mentioned Mainconcept in particular,If not I can't see any reason to use Vegas. It also means that when Magix spruiks Vegas as a 4k editing software, there is a big part of the picture missing.... or should I say sound. You can make the sound and video separately, but what use is that?

GJeffrey wrote on 4/10/2017, 2:51 PM

So are you telling me that Vegas will not render any 4k 5.1 file? 

No.

 I never mentioned Mainconcept in particular

So you post in the wrong thread.

obviously 4k 5.1 files exist, what format do I use

It does, have a look at the render window.

Chuzz wrote on 4/10/2017, 5:59 PM

You not being very helpful. I am TELLING you they are NOT there the AUDIO tabs have Blank fields!. If you don't want to help then don't post GJeffrey. This forum is pretty much a waste of time. Troll if you must, but if you like, how about sharing some proper information instead of just saying 'nope'. Regarding the other thread, it so happened that people started up about the render there and were being more helpful then here so it was entirely appropriate, thanks for your 'çough' help.🤓

GJeffrey wrote on 4/10/2017, 7:14 PM

I am TELLING you they are NOT there the AUDIO tabs have Blank fields

I'm telling you that 5.1 audio can't be rendered with Mainconcept. Wasn't it your question?

Blank field, that's pretty obvious (you'd better read all the posts of this thread intead of trolling?) that is a bug. Revert to b211 or make your own new template.

Cornico wrote on 4/11/2017, 5:49 AM

With build 252 this problem is history. All MC AVC templates render fine.

Chuzz wrote on 4/11/2017, 7:51 AM

With build 252 this problem is history. All MC AVC templates render fine.

Build 252? Downloading now, thankyou for not being weird 😎