{The "Use networked computers" render option no longer shows up as a checkbox. I say good riddance.}

I would miss it because using the Net Render was the failsafe in some instances where Vegas would not render due to memory hangs. For some reason using Net Render would get around that problem.

Erik

It's easy enough to "assign" rendering to an instance of Vegas on another computer using standard network methods.

musicvid

Could you please explain how to assign rendering instance of vegas on another computer ?


Thanks
Chethu

I just open the project from the second computer over the network and render. It's easier if remote desktop is enabled. If you are using SATA drives a gigabity network is suggested.

My experience is that due to licensing issues, the "render with networked computers" was always quite useless. The problem was that unless all the plugins and codecs were also licensed on the networked computers, you couldn't actually do a networked render. This was quite silly because you couldn't legally install the codecs and plugins on more than one computer. I have yet to talk to anyone who as actually been able to use this. Just leaving off a totally useless feature IMHO.

Under my Vegas 8 license, we were allowed to install the Sony application and all components on three computers. Net rendering was just more hassle to get working than it was worth, and the gains were quickly eaten up by the overhead. It was kind of a Spruce Goose.

As Benny Hill would say, "Not a lot o' people know that..."
I was able to place it on three copies on different computers as well ... and my experience was the same; it appeared to be a great opportunity to speed up renders ... but not really ... the transfer of video files is a long enough ordeal in itself, then add rendering and all the associated commands and transfers that need to be accomplished (shheeesh) . . . not worth the hassle. . . and it requires a fast network as well. . . as musicvid indicated. . .

The solution of least resistance is to simply install more RAM - or get a machine with multiple dual-cores (or better) running and working . . .

Until that time ... Earl J.

I haven't had any new renders since the update so I wont cry yet but at first blush I'm with Erik. I have a pretty robust machine and was still often plagued by the dreaded memory error killing a render and no matter what the issue was or what the size of the project checking the Network Render option would work without fail. Why anyone would say "good riddance" to something they don't use but works for others is beyond me. It's always good to have a plan b and I'm disappointed to hear I no longer have that safety net.

- Ray
Underground Planet

I find it funny that net-rendering was one of the "must have" features people said vegas needed several versions ago & now it seems the opinion is it wasn't worth it.

Just goes to show that playing catchup with the other apps doesn't make a good vegas (coughCUDA & 3Dcough)

OK, for some it was a pain, but I did use the network render feature in Vegas9, but on a single machine as a render queuing function.
I did not see any reference to the function being removed on any of the web 'sales' pages for Vegas10 and was badly surprised to find it missing.
Bring it back!

P.S does this mean that render queuing in Production Assistant2 is gone also?

We do use the network rendering extensively using Vegas 8.
We save lot of time using this feature. I am planning to upgrade to Vegas 10 .It is very unfortunate that network Rendering is removed in Vegas 10 !

BRING IT BACK !!

I used it extensively on a single machine as a render queue. It was very useful for this. I agree it needs to come back or just add a render queue function.

rocky

I agree with bastinado, as I also used it as a simple batch render queue that allowed me to continue to work with a single instance of Vegas while rendering.

I would like to know how to batch render queue - I never could get that to work for me - any tips?

Sorry to dig this up if there is a better thread for it....
I do multi cam live event work and end up with TBs of source files that I convert to Cineform for editing.
I'm having a lot of down time in peak periods waiting for conversions.
My bright idea is to have another PC that can churn away in background doing conversions while I keep working. I have about half of components already so is minimal investment.
Most of my converted media resides on external esata Raid 0 drives.
So, finally, What would be the best way to network the 2 PCs so Vegas can be rendering on one and working on the other?
Or, is it easier/possible to get an esata NAS?
Any suggestions on the best way to achieve a working result appreciated.
Cheers
Gerald

Small bump.
Does nobody here work with multiple PCs in their shop?
How do you guys manage your workload in busy times?
Upgrade machine and edit native files? 3930k with 32gb ram is a long way from coping with 5 streams of avchd with light CC. Throw in a stream of 4k and things go from bad to worse....
Any thoughts appreciated

My video editing business is built on a server farm style. The routes are all 1 gig ethernet - NO silly NAS - and no need of fiber optic. Many outboard high-speed drives that are portable run off the mother server they are attached to. Connects USB3.0+ or Thunderbolt. These drives can be swapped to each networked machine.
Live quality previews always done per local machine. Rendering is local to a machine - no cross wire media for this - but events are fast and concurrent across the network.
Seven servers built on Win7 64bit - Vegas13 Pro build 373 all local license.
Investment across hardware, software, and facility about $30,000 over the lifetime of this facility now going on 10 years.

Thanks for that info. Great start.
If only using 2 machines though would a server still be useful ?
The aim being, while working in Vegas on one machine, to send a render to the other pc.

server is just a functionality of workstation - so don't be mis-guided by the term in ways you might be expecting.
AND do not ship files over wire as a rendering process step - just as I stated from the studio scenario I mentioned above. Wire is for direct file transport to get from a to b OR can be used to achieve a low-quality preview - ONLY. Just render when the file is local.

Feature for Rendering with Network.....

Hy I have Vegas Pro 15 Suite and where is the network rendering? Isn`t it there anymore? Why not...it would be so much better....So please tell me MAGIX where is it??????

My rendering takes for 4 min Video and Audio 30 min...

The feature has been gone for some time. You alluded to your pain from long renders but didn't mention the characteristics of your local machine, your network or the speed and availability of machines on your network. I'd work on the throughput of the local machine first.

I have Win 7,24 GB Ram,64 bit Intel Core TM i7 CPU 960q3.20 GHz 3.19 GHZ , GRAKA Radeon RX 470 Graphics