PUBLICIDAD

Welcome to videoedicion.org (v8.3). Please login or sign up.

23 de Abril de 2024, 23:33:25

Login with username, password and session length

Temas Recientes

337 Visitantes, 1 Usuario

Compra y colabora

Si usas estos banners para hacer tus compras, recibiremos una pequeña comisión. ¡Gracias por colaborar!


 




Código VID15 para
un 15% en planes anuales


RENDERIZANDO EN RED

Iniciado por gil003, 14 de Julio de 2005, 20:13:06

Tema anterior - Siguiente tema

gil003

Saludos: este tema es con relacion a la ventaja de renderizar en red con vegas 5 y 6, he estado buscando informacion y lo mas que encontre el manual de vegas 5 de la zona de descargas de Sony Vegas, pero esta en ingles, como mi ingles no es muy tecnico y hay terminos que un traductor interpreta de otra manera, pues me atrevo a solicitar su ayuda para la traduccion de las intrucciones acerca de renderizar en red.
Estas son las especificaciones:

Rendering whit networked computers

Network rendering allows you to designate a specific computer to render the entire output file, our you can distribute a single rendering job among several computers.

·   Distributed network rendering splits the video into segments that are rendered by multiple computers. In this mode, each computer renders a portion of the project, and the rendering sections are then reassembled into a single file by the one computer (called the stitch host). Distributed rendering is a good way to reduce the time it takes to render a project containing a significant amount of processed rendering requires increased disk space and network traffic because each segment must be saved before the final output can file be generated.

Nontemporal video output formats, such as DV or uncompressed Avi, are also well suited for distributed network rendering because segments can be reassembled without re-encoding.
Nondistributed network rendering behaves very much like standard rendering, but you can choose which computer you want to render the project. In this mode, each computer renders a complete file from a Vegas project or the loop region.
If you want to encode the same project to multiple streaming formats and bit rates, it is best to queue up multiple nondistributes jobs because streaming formats use temporal compression and you can assign different renderers to different output formats. If you have a project or output format whit audio only, choose nondistributed rendering because anly video is rendered in the first phase of distributed job.

Both distributed and nondistributed rendering jobs can be queued to be performed as computing resources become available so you can render multiple projects or render the same project in multiple formats.
Rendering using a computer other than your main editing computer allows you to continue working without waiting for the render job to complete.

SETTING UP YOUR COMPUTERS FOR NETWORK RENDERING

The computer that initiates and manages a network render is considered the owner of the job. Each network computer that you use for rendering is called a renderer. The computer that reassembles rendered segments in a distributed rendering job is called THE STITCH HOST.
The computer that is designated to perform a nondistributed network render job is called the RENDER HOST.

To use network  rendering effectively, we recommend the following:
·   256 MB RAM in each renderer.
·   100 Mbps switched local area network.
·   Your media files and output files must be in shared folders, preferably on dedicated file server, All renderers must have permission to read, write, create, and delete files in the shared folders.

Before network rendering begins, a copy of your project will be saved in the shared output folder for use by the renderes. This version will have all media paths remapped based on the Network Render Service file mappings.
DESDE MÉXICO POR UN MUNDO MEJOR

gil003

Setting up a rendering computer:

1.   Install Vegas software as a render-only client. You can Install Vegas software as render-only client on two computers for each Vegas License you purchase. However, certain file formats, such as MPEG-2, AC-3, and MP3, cannot be used render-only clients.
2.   Start the Vegas Network Render Service application (VegSrv50.exe). The service must be running and you must be logged into the computer before you can use it for rendering.
3.   If necessary, you can change the TCP port the render service uses to communicate with other renderers:
a.   Exit the Vegas Network Render Service application if it  is  running.
b.   Open the NetRenderService.config file in a text editor. This file is located in the Vegas installation folder.
c.   Edit the tag in the file to reflect the port you want to use.
d.   Save the file.
e.   Restart the Vegas Network Render Service application.

ADDING RENDERES TO A HOST   
1.   Start the Vegas Network Render Service application (VegSrv50.exe) on the computer you will use to initiate network rendering.
If you do not start  the service before starting a rendering job, it will start automatically, but it will not be visible. Right-click the      icon in the system tray and choose Show from the menu to display the window.

2.   Select the renderers tab. This tab allows you edit the list of computers running the render service. Note: A computer will be displayed on the renderers tab only if you have logged on to windows and the Vegas Network Render Service is running. If the computer is not in an area you can monitor easily, you can use Ctrl+Alt+Delete  to lock the computer after logging on and starting the service..
3.   Click the host box of a blank row in the table, and the type the IP addres or name of the computer you want to use as a renderer. To find your computer, right-click My computer and choose propierties from the shortcut menu to display the System Properties dialog. Click the computer Name Tab, and your computer name is displayed in the full computer name entry.

4. Press enter to connect to the renderer. If the connection is made, The status column will display Ready.
DESDE MÉXICO POR UN MUNDO MEJOR

PUBLICIDAD

El spam de este foro está controlado por CleanTalk