Comments

gandjcarr wrote on 7/18/2013, 7:13 AM

Hi,

The number of tracks you can see has little or nothing to do with your rendering time.  The type of file container you are using, the number of effects and transitions and complexity of the titles you use are most likely the cause of slow rendering.  If you just want do display your poject during playback and get rid of some of the lag in timing, you could just change your video settings by going to File then Program Settings, then Video/Audio tab and adjust the "Movie Display" down to half or quarter resolution.  It should help but won't get it perfect.  If you are using "Preview Rendering"  remember every time you change something in the timeline you need to re-render that part.

George

johnebaker wrote on 7/18/2013, 1:15 PM

Hi

In addition to George's answer and being more specific - the speed of rendering also depends a great deal on your computer specification and the format you are rendering to.

If the source video format and destination format are the same then th speed of rendering will be faster then when they are different.

Working with HD video is very processor intensive and requires a decent quad core computer to get reasonable render speeds.

Come back with yur computer specification and version of Windows you are using, the format of the source video and the final output format your are rendering to eg mp4, mpg, DVD, BD, etc.

John

Last changed by johnebaker on 7/18/2013, 1:15 PM, changed a total of 1 times.

VPX 16, Movie Studio 2025, and earlier versions 2015 and 2016, Music Maker Premium 2024.

PC - running Windows 11 23H2 Professional on Intel i7-8700K 3.2 GHz, 16GB RAM, RTX 2060 6GB 192-bit GDDR6, 1 x 1Tb Sabrent NVME SSD (OS and programs), 2 x 4TB (Data) internal HDD + 1TB internal SSD (Work disc), + 6 ext backup HDDs.

Laptop - Lenovo Legion 5i Phantom - running Windows 11 23H2 on Intel Core i7-10750H, 16GB DDR4-SDRAM, 512GB SSD, 43.9 cm screen Full HD 1920 x 1080, Intel UHD 630 iGPU and NVIDIA GeForce RTX 2060 (6GB GDDR6)

Sony FDR-AX53e Video camera, DJI Osmo Action 3 and Sony HDR-AS30V Sports cams.

asoeli wrote on 7/18/2013, 4:17 PM

In addition to George's and Johns answers: If you will 'get rid of' the unused tracks, go to Movie settings (Shortcut E) and write in the number of tracks you want. 

johnebaker wrote on 7/19/2013, 1:39 AM

Hi

. . . . If you will 'get rid of' the unused tracks, go to Movie settings (Shortcut E) and write in the number of tracks you want. . . .

True, however this only controls the number of available tracks for the project.  Empty tracks do not have any effect on rendering.

Rendering time is determined as given by George and my answers.

John

Last changed by johnebaker on 7/19/2013, 1:39 AM, changed a total of 1 times.

VPX 16, Movie Studio 2025, and earlier versions 2015 and 2016, Music Maker Premium 2024.

PC - running Windows 11 23H2 Professional on Intel i7-8700K 3.2 GHz, 16GB RAM, RTX 2060 6GB 192-bit GDDR6, 1 x 1Tb Sabrent NVME SSD (OS and programs), 2 x 4TB (Data) internal HDD + 1TB internal SSD (Work disc), + 6 ext backup HDDs.

Laptop - Lenovo Legion 5i Phantom - running Windows 11 23H2 on Intel Core i7-10750H, 16GB DDR4-SDRAM, 512GB SSD, 43.9 cm screen Full HD 1920 x 1080, Intel UHD 630 iGPU and NVIDIA GeForce RTX 2060 (6GB GDDR6)

Sony FDR-AX53e Video camera, DJI Osmo Action 3 and Sony HDR-AS30V Sports cams.

Scenestealer wrote on 7/19/2013, 7:41 PM

I have seen it suggested by some of the experienced members that reducing the number of tracks does help preview performance but it is hard to imagine it would be by much.

Still I guess the program would not have the facility to reduce the number of tracks if it did not have some effect...?

Peter

Last changed by Scenestealer on 7/19/2013, 7:41 PM, changed a total of 1 times.

System Specs: Intel 6th Gen i7 6700K 4Ghz O.C.4.6GHz, Asus Z170 Pro Gaming MoBo, 16GB DDR4 2133Mhz RAM, Samsung 850 EVO 512GB SSD system disc WD Black 4TB HDD Video Storage, Nvidia GTX1060 OC 6GB, Win10 Pro 2004, MEP2016, 2022 (V21.0.1.92) Premium and prior, VPX7, VPX12 (V18.0.1.85). Microsoft Surface Pro3 i5 4300U 1.9GHz Max 2.6Ghz, HDGraphics 4400, 4GB Ram 128GB SSD + 64GB Strontium Micro SD card, Win 10Pro 2004, MEP2015 Premium.

gandjcarr wrote on 7/20/2013, 12:25 PM

@ Scenestealer,

The number of available tracks has pretty much nothing to do with rendering.  If it does, it is miniscule.  My answer while technically had some merit and was generically correct, John's answer has by far the biggest impact on rendering time.  I just assumed that the person asking the question had a high end processor with a lot of RAM, bad assumption on my part.  If you don't have a fast multicore processor and a decent amount of RAM, you are basically dead in the water before you start.

George

Scenestealer wrote on 7/21/2013, 6:12 PM

George

Fully agree. My comment about preview performance was really just an aside to the question about track numbers.

Peter

Last changed by Scenestealer on 7/21/2013, 6:12 PM, changed a total of 1 times.

System Specs: Intel 6th Gen i7 6700K 4Ghz O.C.4.6GHz, Asus Z170 Pro Gaming MoBo, 16GB DDR4 2133Mhz RAM, Samsung 850 EVO 512GB SSD system disc WD Black 4TB HDD Video Storage, Nvidia GTX1060 OC 6GB, Win10 Pro 2004, MEP2016, 2022 (V21.0.1.92) Premium and prior, VPX7, VPX12 (V18.0.1.85). Microsoft Surface Pro3 i5 4300U 1.9GHz Max 2.6Ghz, HDGraphics 4400, 4GB Ram 128GB SSD + 64GB Strontium Micro SD card, Win 10Pro 2004, MEP2015 Premium.