Thanks. Hope Magix can figure it out earlier and give us the fix.

The weird thing is as you probably noticed is that the 3D title plays in the project but does not export.

Playback

Export with all nvidia settings. No title.

 

@CubeAce Hi, which 3D title is that?

@KaWai-Lau

This may be just a Windows problem and not effecting all versions. I'm running an enterprise version of Windows 10. It was working for me before the Windows updates KB5017308 which was not distributed to all Windows versions and -KB5017500 Cumulative Update for .NET Framework 3.5, 4.8 and 4.8.1 for Windows 10 Version 21H2 . (both updates arrived the same day.

@Former user

It's affecting any 3D static template for me at this end Gid. The one I show is 'The Movie'.

There are so many computer variables it may not effect your machine, it was just lucky I happened to suffer it as well and found a workaround.

The text shadow bug is also still not fixed in 2022 at least.

There are also release notes on the last Windows updates about known issues which seem close to, but not exactly the same as KeWai-Lau and I am experiencing. I will wait to see if the next Windows update resolves this or not.

Ray.

@KaWai-Lau

Hi,

I tested this on my two computers, one of which is underpowered and I had no problems.

VPX14 20.0.3.169

I tried a few of the Dynamic Templates - Blown by the Wind and Words From Far Away amongst others.

No problems.

Please show screen shots of the interface showing the timeline with the title and the template used, the export interface showing the parameters, and Program Settings/Device Options.

Did you try different options under Program Settings/Device Options/Export?

This could be a Windows 11 problem.

@CubeAce

I tried the same thing in MS2023, including the 3D Title The Movie and had no problems. I tested this 3D title in VPX14 - no problems. I tested the Dynamic Titles in MS2023 - no problems.

I also test the Title Shadow Blur effect in both programs and it seems to have been fixed.

John CB

@CubeAce Ok, the Decorative Basic 3D ones i tried before commenting above worked fine, but that one The Movie was a bit grumpy 1st time i tried it, it wouldn't let me KF it's SPR, but removing it from the timeline & adding it again it worked as expected, Like you say 'so many computer variables' 🤷‍♂️

What is the 'The text shadow bug' ?

PS I'm on Ms 2023. I have now VPX14, i'll try that later reg the OP's post, I need to go back to work now, 😁

@Former user

Hi,

Here is a link to the text shadow bug:

John CB

@Former user

Hi Gid

Just to be clear about the problem. There is no problem with playing the clip in the timeline. It is just when exporting if using nvidia options in all of the programs hardware acceleration boxes (Import / Processing / Export). The title is not included in the export.

Ray.

@CubeAce Yep i understood that, that's what i was doing exporting not just playing, no prob here with all boxes Nvidia

@browj2 Thanks, I remember this now, it might be classed as a partial fix tho, the blur might work but moving the shadow moves the text, it's as if they both move apart from the centre point.

I put a pink rectangle on to show the position/movement

@Former user

Yes, the text moves, but at least we don't get the box edge at 100% blur.

John CB

@Former user

Hi Gid.

Could you put your version into the bottom corner as I did to see if it has anything to do with its positioning in the frame?

The other thing I noticed is I may have run out of vram on my nvidia card. If that's the case then the minimum specs have just shot up for 4K editing on my machine. Some alternative export methods I tried that worked were not also very slow for an export (Think possible hours) and also shot the motherboard ram usage to above 24GBs.

Ray.

@CubeAce Hi, same again no prob, recorded it with Taskmanager showing, but it's bit hard to show because Video Encode is mainly the Geforce screen capture

This is export 3840x2160 without screen capture running, i don't know if will tell you anything tho, it's using 22% but that isn't much, not on my system anyway, it's not maxed out lets put it that way.

@Former user

Hi Gid.

That's a total of 32.1 GB of memory in use and more vram in use than I have. That seems excessive. Even when I can export successfully using Microsoft Warp Device / nvidia / nvidia I'm only using a total of 11 GBs of memory max at 4K unless that video footage is 10 bit. So if not a bug but a lack of the correct ram type, that doesn't look good for me or anyone else with less ram and vram. I am still convinced it due to that Windows update though because it was working for the first week I had that text in the project.

The other problem is using using Microsoft Warp Device / nvidia / nvidia settings is OK for export as it is almost as quick as using nvidia, nvidia, nvidia, but the playback is not as smooth in the project.

Ray.

@CubeAce Hi,  'total of 32.1 GB of memory in use' sorry i don't understand, is that RAM you're ref to?

@Former user

That's the combined vram from the GPU and motherboard ram. Divided up depending on the processes involved. In your instance above I would be 11GBs short of vram from my GPU.

Hi Browj2,

I used Rain of Letters template for testing. In the first row, left side screenshot shows the template working well. The other two following screenshots show the program setting and device options. The right screenshot in the second row shows the template title disappears after rendering. The movie codec is 4k xavc s.

I tried using "T" button with animation moving from left to right in the title editor. It works well.

Thank you for helping me to investigate the problem.

@browj2 @KaWai-Lau   VPX14, Rain of Letters, again no prob, all boxes Nvidia,

@CubeAce This is a pic of it playing, (after i'd exported it a few times, changing things each time) RAM is normally about 14%, (at idle RAM is 12%) I had Premiere Pro open & an online tutorial vid running in the pics above, i should've closed them but my system is using more simply because it has more to use, your's would just run slower wouldn't it?

I know you can't compare my system to yours but there must be something more to this than just those boxes in settings with Nvidia ?

This is an unknown problem for me. Thanks anyway.

Hi Gid.

There are not many clues from Magix as to how the program works but we do know that a lot of data is sent to ram. That the amount of ram and which ram is used changes with the setup of how things are rendered by which components depending on the choices made in the Import / Processing / Export boxes or if things get really bad disable the hardware acceleration altogether. Disabling hardware acceleration altogether curiously lowers the total amount of ram used during export. (at least at my end).

I think the speed of export is a separate issue and is not just down to the speed of the ram but also the bus width of the GPU (your nvidia card has a bus width three times wider than mine as well as more processing cores and ram), and how many CPU cores can work in parallel. Disk read write speeds would also come into the equation for export times.

The manual suggests that if not enough ram is present sometimes things don't get written. In the instance below it mentions proxy files but by implication it could be other files won't get written as well. Now in this instance my motherboard ram is not maxed out but my nvidia card vram is and that as far as I'm aware does the bulk of the 3D rendering during export.

Your examples so far have not included changing the title and has been left 'As is'. I would be happier if you changed the wording of the Title so as to 'change' the instructions within the program as I think that would be more representative of what someone suffering the problem would do. I still expect it to work though.

On reflection though it may have nothing to do with the Windows update because the other thing that changed during the time between the effect working and not working was the amount of other things such as adding clips and processing them (colour adjustment, contrast, etc) also increased. That too could have caused the need for more vram to be available or there is not enough processing power within my nvidia card to cope but as it is playing during playback so I'm not overly sure of anything too much. Just looking for changes in component usage between the playback and export using the task manager which is not that scientific.

@browj2

Hi John.

It appears you are correct and that the shadow bug is no more. I hadn't tried it recently.

Ray.

[Edit]

I too have tried just the same 3D title with one video clip above it and it exported with no problem.

It would seem to be an accumulative problem dependent on the total amount of processing needed at any one moment along an entire project.

My conclusion is it is hardware related with the nvidia GPU somewhere (in my system at least, and @KaWai-Lau has the same amount of vram that I have) unless someone can push another system hard enough to replicate the problem.

@CubeAce

@CubeAce

Hi Ray,

As I said, I tried the titles on 2 computers. My laptop has 8GB, no separate graphics card. The project was 1920x1080, not 4K, Windows 10. No problems with the titles during or after export. GID has no problems with 4K and a title.

Surely your computer should be able to handle one short video clip with the Dynamic title.

The only thing that I can think of is that the OP has Windows 11.

@Former user

OT. That reminds me, I have to make 2 drawers for my workbench. For some reason the upper left and right drawers are missing and were when we bought the place a year ago. Unfortunately, that project is way down the list. I'm currently scraping flaking paint from the exterior upstairs dormers, sanding, patching and painting. Next is similar work on the garage, followed by stone masonry work, then winterizing.

John CB

@browj2 @Former user

Hi John.

That is not the issue. The issue is not being able to use the nvidia card for all hardware acceleration settings for export when it plays with those settings and objects within the program and not even having to revert to using proxy files. Does that not strike you as unusual? What changes that makes that happen? I suspect but don't know that the difference is playback does not need to encode which is an extra step and possibly overloads the amount of vram needed but that is just a guess on my part and is quite possibly more complicated than that.

Not using the nvidia for export increases the export time and the amount of motherboard ram goes well beyond the recommended 8GB as advertised in the specs. These are not third party graphics but offered as a part of the base program. It is clearly not a bug if others can accomplish the task (But all those that have using only nvidia on their program settings are using a higher specked graphics card) but it makes decisions about how to set the program up more difficult for some users especially if half way through a project, something that worked say two hours earlier suddenly doesn't.

Personally I don't care as I nearly always find a workaround but I can understand why other less experienced users get confused or frustrated. I do however find it annoying.

Exporting a static 3D title worked better in older releases of the program as the processing requirements were not as stringent. It can still work if the workload of the project overall is not that great but why just because more clips are added to a project does it suddenly stop working? (At least at my end and possibly for @KaWai-Lau ).

Also why even compare a project with only an HD resolution to a 4K one?

If someone tells you they have a problem then we should accept it at face value until someone can figure out what is going wrong or can find a workaround. This is why it is good to have active members with different machines of various capabilities. At least then we can work out if the problem can be replicated or at which point a problem no longer becomes a problem or if it is indeed a bug.

Ray.