Version 2022

mojoaudioguru schreef op 19.09.2021 om 06:50 uur

I'm trying to render a BDR, but I keep getting "Error Encoding Menu" It's the same menu that I've always used in previous versions of MEP+. I can't make heads nor tails out of all the nomenclature. My computer is up to specs. The rendering of the 3 hour wedding was done in less than real time. However, when I get to the menu encoding part, it pops up with a failed notice. Here is the report:

2021/09/18 23:30:56 [INFO] [UserAction]: Start MAGIX Video deluxe Plus(21.0.1.85)
2021/09/18 23:30:56 [INFO] [_Common]: DllPool::Host = true
2021/09/18 23:30:57 [INFO] [_Common]: Initial GPU adapter [#0xbef1]: NVIDIA GeForce GTX 1050 Ti
2021/09/18 23:30:57 [INFO] [_Common]: Initial video mode: Standard mode (Direct3D, hardware acceleration)
2021/09/18 23:31:09 [INFO] [_Common]: RegisterApplicationForRestart()=Result=0
2021/09/18 23:31:22 [INFO] [UserAction]: Load project Becky & AJ BDR Stereo part one II.MVP
2021/09/18 23:31:23 [INFO] [_Common]: CProgressDlg1Manager::CProgressDlg1Manager: semantic error - progress dialog not null
2021/09/18 23:31:30 [INFO] [_Common]: CProgressDlg1Manager::CProgressDlg1Manager: semantic error - progress dialog not null
2021/09/18 23:31:43 [ERROR] [Import]: no import module for image file:
2021/09/18 23:31:43 [ERROR] [Import]: no import module for image file:
2021/09/18 23:31:43 [ERROR] [Import]: no import module for image file:
2021/09/18 23:31:43 [ERROR] [Import]: no import module for image file:
2021/09/18 23:31:43 [ERROR] [Import]: no import module for image file:
2021/09/18 23:31:43 [ERROR] [Import]: no import module for image file:
2021/09/18 23:31:43 [ERROR] [Import]: no import module for image file:
2021/09/18 23:31:43 [ERROR] [Import]: no import module for image file:
2021/09/18 23:31:54 [INFO] [UserAction]: Switch main tab to Brenntab
2021/09/18 23:31:59 [FATAL] [MX3dVfxManager]: MxGPUVideoMode::CreateCacheTextures () Hint: Creating of cache texture 27 of 35 failed. Out of resources
2021/09/18 23:32:00 [FATAL] [MX3dVfxManager]: MxGPUVideoMode::CreateCacheTextures () Hint: Creating of cache texture 27 of 35 failed. Out of resources
2021/09/18 23:32:49 [INFO] [DiscMaker]: BurnSupport: 2 device(s) found
2021/09/18 23:32:49 [WARNING] [DiscMaker]: setting no speed limit
2021/09/18 23:32:49 [WARNING] [DiscMaker]: DBK CBurnDevSupport::InvalidateDiscInfo(): 16 - burn support - invalid device.
2021/09/18 23:32:52 [ERROR] [DiscMaker]: AVSDK Message - Cannot get device/media specific information -> functionality is not provided by device or by system
2021/09/18 23:33:01 [ERROR] [DiscMaker]: AVSDK Message - Cannot get device/media specific information -> functionality is not provided by device or by system
2021/09/18 23:33:03 [ERROR] [DiscMaker]: AVSDK Message - Cannot get device/media specific information -> functionality is not provided by device or by system
2021/09/18 23:33:09 [INFO] [DiscMaker]: Step 1 of 7, Encoding movie 1 ...
2021/09/18 23:33:09 [INFO] [DiscMaker]: Step 1 done
2021/09/18 23:33:09 [INFO] [DiscMaker]: Step 2 of 7, Encoding movie 2 ...
2021/09/18 23:33:09 [INFO] [DiscMaker]: Step 2 done
2021/09/18 23:33:10 [INFO] [DiscMaker]: Step 3 of 7, Encoding movie menu...
2021/09/18 23:33:10 [INFO] [_Common]: Export with GPU("NVIDIA GeForce GTX 1050 Ti")-FX and HW encoding rendering to C:\Users\Jose J. Aguado\Documents\MAGIX\Movie Edit Pro Plus\Disc Images\AVCHD Image Becky_&_AJ_BDR_Stereo_part_one_II\BDMV\STREAM\00002.m2ts from 0 to 3504305 started (MxMpeg4Intel-AVCHD|1920x1080i|1.77778|29.97 FPS|15000 kbit/s||2 CHN|48000 Hz|384 kbit/s)
2021/09/18 23:33:37 [INFO] [_Common]: Export 73.0s finished successful (Duration=26.8s)
2021/09/18 23:33:37 [FATAL] [MX3dVfxManager]: MxGPUVideoMode::CreateCacheTextures () Hint: Creating of cache texture 27 of 35 failed. Out of resources
2021/09/18 23:33:37 [INFO] [_Common]: Export with GPU("NVIDIA GeForce GTX 1050 Ti")-FX and HW encoding rendering to C:\Users\Jose J. Aguado\Documents\MAGIX\Movie Edit Pro Plus\Disc Images\AVCHD Image Becky_&_AJ_BDR_Stereo_part_one_II\BDMV\STREAM\00003.m2ts from 0 to 3504305 started (MxMpeg4Intel-AVCHD|1920x1080i|1.77778|29.97 FPS|15000 kbit/s||2 CHN|48000 Hz|384 kbit/s)
2021/09/18 23:33:58 [INFO] [_Common]: Export 73.0s finished successful (Duration=21.3s)
2021/09/18 23:33:58 [FATAL] [MX3dVfxManager]: MxGPUVideoMode::CreateCacheTextures () Hint: Creating of cache texture 27 of 35 failed. Out of resources
2021/09/18 23:33:58 [INFO] [DiscMaker]: Step 3 done
2021/09/18 23:33:58 [INFO] [DiscMaker]: Step 4 of 7, Encoding chapter menu 1 ...
2021/09/18 23:33:58 [INFO] [DiscMaker]: ConvertBitmapToMPEGForMenu: BitmapResolution=1920x1080
2021/09/18 23:33:59 [FATAL] [MPEGIntel]: DP4::IntelVideoEncoder::Encode: SEH exception 0xC0000005: access violation
2021/09/18 23:33:59 [FATAL] [MPEGIntel]: EncodeError |DP4 errno=0x8000FFFF: Catastrophic failure
|buffer address=0x000000003808A428, size=3110440 |where=VideoEncoderBase::Encode called EncodeFrame
2021/09/18 23:33:59 [FATAL] [MPEGIntel]: VideoOnlyPipeline::EncodeVideo frame 0: HardwareEncodeError
2021/09/18 23:33:59 [FATAL] [DiscMaker]: ConvertBitmapToMPEGForMenu: CInfoException: 0x8004002b - WriteVideoFrame failed
2021/09/18 23:33:59 [FATAL] [DiscMaker]: CBEncodeStillImage: CInfoException: 0x80004005
2021/09/18 23:33:59 [INFO] [DiscMaker]: Step 4 done
2021/09/18 23:33:59 [FATAL] [DiscMaker]: PrepareDVDVideoFiles() failed with errNo 13 - menu rendering failed
2021/09/18 23:33:59 [FATAL] [DiscMaker]: !!! DBK BurnProject: 11 - menu encoding failed !!!

I am running Windows 10 Pro, up to date version. My CPU is an Intel i7-7700K, overclocked - stable, @ 4.7 GHz. I have 24 gig of DDR4 RAM. The GPUs are the Intel HD 630 and an NVidia GTX 1050Ti, with 4 gig of DDR5 RAM. I have employed this menu for wedding videos, since it was first introduced by Magix, years ago. Not understanding why this new 2022 version is not allowing the menu to encode. Does anyone have any answers? Has anyone experienced this with this new version? Can anyone understand all this info above?

Reacties

CubeAce schreef op 21.09.2021 om 02:44 uur

@mojoaudioguru

Hi.

I may be reading this wrong but it may be possible your nvidia card is being over-stressed.

Try going to File / Settings / Program / Device options and change Export to Microsoft WARP device.

I have checked that configuration works on my machine. It should lower the amount of work the nvidia card is doing. The export may then work but be slower. If it doesn't then it may be possible that your recorder is not being recognised.

Ray.

mojoaudioguru schreef op 21.09.2021 om 03:33 uur

So, after trial and error, I figured out that I had to choose the "CPU" feature in the processor menu, in order for the menu to be encoded. It added 12 minutes to the rendering process. I had to pick "Use all" after the failed rendering process, which would fail at the menu being encoded. My NVidia card has 4 gig of DDR5 RAM. I doubt it got over stressed. There has to be a flaw or glitch in this version of MEP+. Someone should alert Magix about it. But, I do thank you for your suggestion.

CubeAce schreef op 21.09.2021 om 08:05 uur

@mojoaudioguru

Hi. In this instance I don't think the amount of vram is the problem but the way the card is being used to create textures. It starts just before this line.

2021/09/18 23:33:58 [FATAL] [MX3dVfxManager]: MxGPUVideoMode::CreateCacheTextures () Hint: Creating of cache texture 27 of 35 failed. Out of resources

Which then passes down the line to these ones.

2021/09/18 23:33:59 [FATAL] [MPEGIntel]: DP4::IntelVideoEncoder::Encode: SEH exception 0xC0000005: access violation
2021/09/18 23:33:59 [FATAL] [MPEGIntel]: EncodeError |DP4 errno=0x8000FFFF: Catastrophic failure
|buffer address=0x000000003808A428, size=3110440 |where=VideoEncoderBase::Encode called

Which seems to infer it's how the two GPUs are sharing the load for pixel shading individual frames.

By all means you should start a ticket with Magix but I can't replicate your problem and it does seem to be hardware based.

Ray.

mojoaudioguru schreef op 21.09.2021 om 15:34 uur

Thank you for your insights. How does one go about creating a 'ticket' with Magix? It's been years since I've done it, and they've made it so difficult to get a hold of anyone. (There once was I time when I could just pick up the phone and call them, seriously) Doesn't anyone from Magix actually monitor this forum? There must be a way to balance this shader issue. I tried various combinations of GPU assignments in the menu, to no avail, outside of just letting it fail the burn at the menu render, then going back and changing the Intel GPU to CPU, in the menu rendering process, and choosing "Use All" to get it to render completely. Which adds 12 to 15 additional minutes to the process, and is something no one should have to do. I do however appreciate your assistance in this matter. Thank you once again.

emmrecs schreef op 21.09.2021 om 16:38 uur

@mojoaudioguru

Use this page to create a Support Ticket. Just make sure you follow through and check each subsequent page.

HTH

Jeff

mojoaudioguru schreef op 21.09.2021 om 17:04 uur

Thank you for your advice. However, this page, and subsequent pages are too discombobulated and in precise. I'd spend all day there, and still accomplish nothing. I'll just keep on employing my workaround until someone can actually reach Magix and they issue a patch / fix for this. Although, I haven't seen any patches in over a year, with 2021, so I'm not even sure I can get any. My internet was down for several days once, and just to see what would happen, I pressed update, and I got the usual, 'No updates available. ' Yet, I had no internet, whatsoever, for it to go online and check. So I don't believe that even works. This is ridiculous and unacceptable. Magix is not what it once was.

browj2 schreef op 21.09.2021 om 17:22 uur

@mojoaudioguru

However, this page, and subsequent pages are too discombobulated and in precise.

No, it's not. It's easy.

Click on Support at the top of the forum
Click on Ask Support
Click on your Category, presumably Video
Which Product? Click on Movie Edit Pro
Click on Search for other solutions
Put in Short Description which is actually the Subject line of your ticket that you want to submit
Click on Find a Solution
Scroll down - click on the big blue button that says SEND A SUPPORT REQUEST
Describe your problem and click on Continue

The rest should be obvious.

Magix needs to know which product and that you have at least looked at the FAQ's before submitting a ticket.

John CB

mojoaudioguru schreef op 21.09.2021 om 17:30 uur

Now, that's what I'm talking about. Clarity. Thank you. It's a long and tedious process. After several pages, one loses interest. Especially when dealing with an issue that already creates major frustration. I'll give it another go, but I don't know if it'll work. With my luck, they'll tell me it's my computer. Which ran beautifully with MEP 2021+, without issues. Adding to my frustrations. Thank you, just the same.

CubeAce schreef op 21.09.2021 om 20:44 uur

@mojoaudioguru

I do wish that sometimes they would be a bit more specific and test more.

A disclaimer that not all hardware can be accounted for to work within the complexity of the code of the program is a fair comment but maybe they should not try to say basically what worked in the last version will work in the current version. They must know if a chip using Pascal architecture compared to one using Turing would work or not. Both on the surface looking the same for vram capacity which is what Magix quotes and Direct X compatibility but nothing on the actual computing power on the chip. Turing has about twice the amount of transistors as Pascal and about a third more shading units.

Why this seems to have become a problem I have no idea.

Again, I could be wrong but it would be nice to find out.

Ray.

mojoaudioguru schreef op 22.09.2021 om 17:37 uur

I agree, wholeheartedly. In the past, Magix went out of their way to accommodate its customers. I literally would have conversations, over the phone, with developers and staff members. When things changed in 2015 / 2016, it all went south. I've built my last 3 desktop computers. The average lifespan is 4 years. This one has a year to go. I know that the next one has to be up to date, and slightly beyond, simply because once it's built, it already becomes obsolete. Wishing that Magix be what it once was, is futile, at best. But, the least that they could do is, make a software that truly is flaw free, before releasing it to the unsuspecting public. Especially with their new 'subscription' feature. I do thank you all for your assistance, however. If it were not for all of you and your consideration, I would have dumped this software, years ago.

CubeAce schreef op 22.09.2021 om 20:23 uur

@mojoaudioguru

I am in pretty much the same boat as yourself. Self build to try to get a four to five year life span out of it. and on occasion have the odd bit of trouble with software releases.

I wish it was just Magix but the communication side of dealing with any internet company now is ridiculous.

Even my service provider makes it easy to upgrade my package with one phone call. Trying to tell them my connection has been severed by builders next door is impossible. Trying to unsubscribe to anything can be horrendously difficult.

My chosen option now is to really look at all the specs of any offered software and try to deduce what it all really means. If I am in any doubt I delay further upgrades until I find someone with a similar setup not experiencing problems. If necessary I will then not upgrade at all until my system is rebuilt or I have funds to replace maybe the one or two components I need once I've figured out what they are. The last upgrade I made was to my graphics card but even now I think I should have gone for a newer 6GB Turing version.

Ray.