Render time oh the render time...

GameHard4.0 wrote on 1/10/2017, 2:55 PM

Could we please have a proper answere regarding the horrible rendertime on what was supposedly a better program (Magix Movie edit pro pluss) By the way its not. No hardware acceleration. And please dont tell people to go check there nvidia settings and go look for settings that are only on Laptops..... Please try to correct the problem with your product. We pay decent money for this, and then we cant do the work. I`m on a Nvidia geforce 1080. And i really dont wanna step back to a older version of Magix, cause it always freezes up and crashes.

Comments

robert.nawrowski wrote on 1/11/2017, 5:22 AM

Same for me, i7, 32 GB RAM, GTX 1080 on PC and cant use my Pro X :( Render time without hardware acceleration is so bad. Have to use h264 for YouTube and it is impossible :/

GameHard4.0 wrote on 1/11/2017, 5:45 AM

Our pc specs are definitly up to par, so its very sad to see that this program cant take the benefit from this. Also i have been seeing major quality loss when rendering with the latest programs from Magix. The Hardware acceleration was even a problem in 2014 version. I`m not expecting any answeres from Magix regarding the rendering issues with there products. Maybe its time to move on to something better....

johnebaker wrote on 1/11/2017, 7:42 AM

Hi

@GameHard4.0 and robert.nawrowski

Did you read this topic - page 2 in particular is relevant?

If you have the MainConcept encoder and the new AVC/H.264 Video Encoder Wrapper installed, MEP looks like it is ignoring the HWA setting - the MC codec appears to automatically use the appropriate graphics GPU if available.

If you are using the Intel codec - see this post in the above topic.

NVidia have stopped supporting CUDA in preference to their new offering NVENC which is not widely supported in many NLE programs - possibly due to its reported poorer quality compared to Intel's QuickSync - see the second link above re using QuickSync.

Also you have mentioned slow render, however you have given no details in particular:

  1. Version of Movie Edit Pro being used and if patched up to date
  2. Format exporting to and settings used
  3. Source material format
  4. Complexity of the timeline
  5. Any special effects added to objects on the timeline
  6. Time taken for rendering

HTH

John EB

Last changed by johnebaker on 1/11/2017, 7:54 AM, changed a total of 3 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 24H2 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.

robert.nawrowski wrote on 1/11/2017, 11:20 AM

Hi John, I dont have main concept. Why i have to pay for standard thing like encoder to use it normally? This answear is not for me sorry. I buy PC, i bu Magix Pro X. It is slower than my laptopo with gtx860m from 4 years in past. There is no information on ur site i doesnt work properly with new Nvidia cards. :/

johnebaker wrote on 1/11/2017, 3:53 PM

Hi

. . . . Why i have to pay for standard thing like encoder to use it normally? . . . .

'If you have the MainConcept encoder' does not mean you have to buy the MainConcept encoder.

. . . . There is no information on ur site i doesnt work properly with new Nvidia cards . . . .

This site is provided by Magix for the members and run by the members to discuss topics, issues and other Magix related issues and help each other.

Did you read the response from Scenestealer to Yamane in the second post I linked to above? You do not use the NVidia card for HWA, instead use Intel QuickSync.

John EB

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 24H2 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.

robert.nawrowski wrote on 1/11/2017, 4:19 PM

But it is for laptops. On PC i dont have optimus technology to change from Nvidia to Intel.

About main concept, if i click on activation there is screen i have to buy it. U say if i do so the render will be much quicker with Nvidia?

Sorry for saying there is no information. I didnt see it.

Ok, so what i have to do, to use my PC with gtx 1080 and use HWA? Please help me. I have Pro X and i am using Premiere Pro because of render time :/

GameHard4.0 wrote on 1/11/2017, 5:38 PM

It would be very nice with just a simple answer, instead of the same nonsens everytime, its like they make you jump thru hoops, We are on stationary Computers, NO Laptop. Optimus technology is NOT an Option for us. Is there anything at all we can do ? Or is it just a fact that Hardware acceleration don`t work with the new Nvidia cards ? It sure would be nice to know this upfront, there was no info on the main page regarding this. I think its very sad, cause i really like Magix its a easy and very understandable program.

Scenestealer wrote on 1/11/2017, 5:38 PM

Hi Robert

But it is for laptops. On PC i dont have optimus technology to change from Nvidia to Intel.

I think you misunderstood my comments in the topic you raised about this early last year. You do not need Optimus to use both GPUs in your present system, which is very similar to mine. In that thread I was trying to explain why one of your laptops worked and one did not.

There is plenty of information in those topics that John EB has linked to about getting your system to use either or both GPUs with VPX. It should also be clear that whilst the Nvidia can not export with HWA encoding via Cuda, it can still assist with parallel processing of the effects on the Nvidia GPU during export and preview/playback.

About main concept, if i click on activation there is screen i have to buy it. U say if i do so the render will be much quicker with Nvidia?

It is true that in recent versions of Magix that you do need to purchase the Mainconcept H264 Codec to use it. But a trick here is that if you have an older version (which you appear to have), like 2014 which came with the codec included in Plus Versions, then you should install MEP2014 on your new PC and activate the MC codec for free, after which it will be available to VPX7.

Ss

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.

GameHard4.0 wrote on 1/11/2017, 5:48 PM

How do you go about installing the Mainconcept H264 Codec in the older version of Magix ? Like the 2014 version. By the way thank you for this reply, feel like this might actually get us somewhere.

Scenestealer wrote on 1/12/2017, 12:48 AM

its like they make you jump thru hoops,

Who is "they"? Anyone responding on this forum is a user just like yourself except we have done a lot of "jumping through hoops" to find answers that might also help other users. There are no simple answers when it comes to complex software interfacing with a myriad of computer configurations, so a bit less attitude would be appreciated. The below worked for me and several other users, but other people have tried it and were not successful, that's the simple answer.

Or is it just a fact that Hardware acceleration don`t work with the new Nvidia cards ? It sure would be nice to know this upfront, there was no info on the main page regarding this.

Really......do you expect companies to sell products by telling you every single thing they will NOT do?

If you search this site you will see that Hardware Acceleration is not just about encoding for export via Nvidia Cuda.

How do you go about installing the Mainconcept H264 Codec in the older version of Magix ? Like the 2014 version.

What you do is install your copy of a 32 bit version, in my case MEP2014, then activate the MPEG2 codec by opening the HDV record window. This prompts you do download the MPEG2 Codec and activate, and because this was free along with the MC MPEG4 codec in those versions, this sequence then allows you to download the MC Mpeg4 codec after setting up to encode an MPEG4 in 2014 and following the subsequent prompts. Because these codecs are then present on your 64bit machine you should be able to access them via MEP2016, 2017,VPX7, and VPX8.

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.

robert.nawrowski wrote on 1/12/2017, 3:42 AM

Ok friends, so if this is so easy... please tell me what to do in case sameone is installing Magix Product on PC with GTX. There is no tutorial here and plenty of new topics about this problem. Maybe we can create something helpful?

 

EDIT: Ok, bought main concept for Pro X. Seems it is working and using my gtx 1080. Give me few hours to make settings perfect and i will let u know ;)

Scenestealer wrote on 1/12/2017, 4:33 AM

Ok friends, so if this is so easy...

Sorry Robert, you misunderstand again. As I said in my last response above yours "there are no simple answers when it comes to complex software interfacing with a myriad of computer configurations". In the next sentence I was being ironic when I referred to "the simple answer".

I appreciate that English may not be your first language (?) which is making it harder for you, but I think all the options are discussed pretty extensively here and in the links John EB supplied in his first response.

Ss

Edit: Just refreshed the screen and saw your edit - let us know how it goes.

Last changed by Scenestealer on 1/12/2017, 4:38 AM, 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.

robert.nawrowski wrote on 1/12/2017, 7:49 AM

Ok, i have one question. In the picture. There is soft for rendering. There is CUDA to choose but i have error than. I have to use soft + GPU for transitions (it affects GPU usage 10-50%) or i can use CUDA and change something?

Scenestealer wrote on 1/15/2017, 5:04 PM

Hi Robert

or i can use CUDA and change something?

Avoid anything that mentions CUDA as this will cause the error message. Just make sure you tick the box in the "Program Settings" that says "Use Hardware acceleration for Export if available" and then use a Mainconcept standard (software) encode template. If it can it will activate some form of acceleration during export.

I see from your first screen shot that you are using a modified Preset template. Try to use a Preset (unmodified) template wherever possible. Do not click apply at the bottom of the advanced settings as this seems to reset a preset template to a completely different bit rate etc., in fact do not even enter the advanced encoder setting as I am seeing some inconsistent behaviour on my installation.

Peter
 

 

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.