And I might add, Vegas 15 actually renders beautifully using the new codec as long as I use the batch script or Vegasaur's transcoder do I doubt it is the encoder.

-- tom

So, here is my response from Magix support:

Thank you for your message.
There are multiple possible causes to this problem. Here are some potential
solution:
1. Please try changing the bitrate to 1 that was in the drop-down
selection for that template. 
2. Select a standard output resolution, like 1920 x 1080 and so on, because
some codecs only render to industry standard video resolutions.
3. If you install some codecs don't come with Vegas Pro 15, please uninstall
them and re-install Vegas Pro 15.

Best regards,
X*** W***
MAGIX Software GmbH

=========================================
 

What we have here is a failure to communicate. Forget we ever mentioned the word "render". The dialog box to render won't even open without returning the error. All of the above is irrelevant since I can't even reach the render settings dialog. I have never installed a codec apart from standard Windows, Vegas or HitFilm since Vegas 3. Plus, all works well with Vegas 14.

Yes - they are not understanding that there is no option to render

Peter, that actually was one of the first things I tried.

Thats good to know.

But, just to be clear. We're not even getting to the point of creating a media file, unless Vegas creates some kind of media file to initiate the opening of the Render as dialog box.

And exactly that is the point where the FileIO dll may come into the play. You conciser that Vegas checks the project settings and propose only the formats that fit.

I’m just looking for a way to reproduce this problem to pass it to the developers.

"1. Please try changing the bitrate to 1 that was in the drop-down
selection for that template. "

Duh... 🙈 #speechless

I’m just looking for a way to reproduce this problem to pass it to the developers.

Ok, seriously, wish I can reproduce this issue, but this is really out of idea... (and I never had this issue since the first time using Vegas Pro). So I believe something not right with your system that caused Vegas fail to run a code...

But, so far my thought on this:

- Do you change any of Vegas' default settings, like Installation paths, preference settings, temp settings, etc. ?

- Do you install any 3rd party video codecs or codec pack? (ok, for monoparadox, the answer to this is NONE)

- Any other non-familiar Windows applications that is not usually installed which perhaps affecting Vegas Pro?

I have this same issue (render as dialog does not appears, get error message instead, but batch render is ok). But there was a clue here on the last post as to what the issue is. In my system, my documents folder points to a NAS/Network location. This forces internal settings to put many things on the networked/NAS documents drive. However the dialog fails if setting "Render Path" is a network drive.

In my case, I fixed the problem by changing the system setting "Render Path", which is about 3/4 the way down on internal settings, to point to a non-network drive folder. (You get to system setting by control-shift options-->preferences-->Internal). Once the dialog comes up, if you change the render folder back to a network folder, it will run file for that run but will fail on the next run.

The techs need to fix the software to allow the documents folder to be on a network/NAS drive, and tolerate as network/NAS setting for "Render Path". It seems like this one setting is the only issue so far for me. Version 14 was fine with the documents folder on a network/NAS drive.

I don't know if you have the same or similar problem, but I hope this works for you.

BINGO! Thanks, Don!

I had considered the network issue but didn't dig deep enough into the internal menu, even experimenting by changing "rendered media path". I guess I just gave up that "path" after it didn't solve the problem.

I have run into issues such as this in the past, although it's been some time ago it seems.

Some lessons here for Vegas support and coders -- but they can figure them out.

For users, squeaky wheels do get oiled once in a while.

Again, thanks!

And Don, you need to get off the beach and monitoring Vegas forums more often! ;-)

-- tom

So it is a network drive location issue? @iggy097, can you also confirm?

On my main machine it renders to the local machine. However two files are located on a network drive. Once the error occurs I can open a brand new project and try to render anything ( all local files ) and the error will pop up.

On my second machine I am pulling the files of my main machine to bulk render.

I guess it's possible that it's something network related initially and then it locks up or something making any "render as" fail.

I'll try adding the two network files to my local hard drive and see if any issues occur after that. I don't render to my NAS or have anything cached there as far as I know. Everything is rendered and cached to a local hard disk ( solid state drives ) and then moved over to the NAS after.

I have probably rendered 20-30 projects since swapping over to 15 and have had the error occur maybe 5 times on the main machine and once on the secondary.

Iggy, moving the files will not solve the problem. You must change the path in the Vegas internal preferences per don-Robertson's post above. You reach internal preferences by holding the shift key when opening preferences. Then open the internal tab. Change the path there from your network location to a valid local folder assuming it is set to a network location.

-- tom

Mine is not set to a network path - but to one my local drives

So the error has just popped up again - I had just taken one movie ( that was on my NAS - not sure if that makes a difference ) - and I batch rendered it to a WMV,and 2 seperate MP4 files. I then tried to render it ( not batch ) to an mp4 and got the above mentioned error.

Just to test it out - I tried putting all media on local drive and rendering. No dice.

Iggy, just to make sure we're on the same wavelength. You're obviously using a NAS which introduces the possibility of network issues. What is your default Windows 10 setting for file save? Are your documents saved to the NAS by default?

-- tom

Nothing gets saved to the NAS it all gets saved locally - documents, movies etc

hmmm. Don't know what to say. It seems the Vegas programmers did change something from version 14 to exacerbate the issue. Perhaps this thread will give them a clue that leads to a correction in the next update. My suggestion would be to compare any of the paths impacting rendering found in the settings hidden menu (internal tab) and see if they are changing from when you reset the defaults when starting Vegas (and it presumably works) to when your error occurs. You can search for the word "render" in the hidden settings menu to bring up all the settings that have to do with rendering. Look at the paths and see if any are pointed to a network location.

Just to confirm, I changed the setting on my second computer and it solved the issue on that one, too.

-- tom

Ok - so you guys were correct. The error occurs after Vegas tries to change the render path to my NAS. I recorded the process - maybe it will help someone else who has this issue, or I can send it to the developers.

Ok - so you guys were correct. The error occurs after Vegas tries to change the render path to my NAS. I recorded the process - maybe it will help someone else who has this issue, or I can send it to the developers

Iggy, glad you got that figured out. It should be a fairly easy bug for the developers to fix. One of those things that crops up with a limited testing.

-- tom

We have reproduced the problem. The development team will try to get a fix for this into an early update of Vegas 15. One workaround that I found was to map the network render location. That seemed to work on my system.

-Derek

I had this problem. No help was found through a support request but a response in my thread led me to this thread and the solution:

"In my case, I fixed the problem by changing the system setting "Render Path", which is about 3/4 the way down on internal settings, to point to a non-network drive folder. (You get to system setting by control-shift options-->preferences-->Internal)."

Awesome! I've been fighting this problem ever since I upgraded to 15. Magix tech support couldn't help. This fixed my problem as well. Thank you all for this information!

Thanks much man! You saved my life! Ctrl+shift to launch is solution! So every time I should tolerate option reseting when I met that rendering can't problem?