Update Patch to 22.0.3.167

Thanks for the reply.

I do have Windows 11 but Smart App Control is greyed out i.e. when I search for it then click on it absolutely nothing happens. I assume this is because I have Norton 360 installed - it's a good program but it does like it's own way.

I've disabled everything I can in Norton but I still cannot install the patch. Luckily the installer gives the opportuniity to continue with the existing version.

AndyW

CubeAce wrote on 11/21/2022, 9:03 AM

@me_again @Marc-Goder

I just installed the update with Win 10 and no install issues. Did not even turn off any anti-virus protection.

Just now trying to see if there are any playback performance improvements.

Ray.

CubeAce wrote on 11/21/2022, 9:25 AM

@me_again @Marc-Goder

Hi.

Maybe no install issues but the audio mixer is not remembering when the limiter is activated on the master fader channel on my system. Trying to activate the limiter has resulted in the program crashing straight away. Twice now. Crash report is.

----------------------------------------------------------------------
MAGIX Video Pro X14 20.11.2022 00:50
----------------------------------------------------------------------
CrashDump 20221120_005028_v20.0.3.175.dmp successfully written

Error in module "(null)" (Load address: 0xFFFFFFFFFFFFFFFF) to address 0x0000000274677930 (Exception 0xc0000005 "ACCESS_VIOLATION")

Main Thread   (ThreadID: 00003b9c)
0000000274677928   62 72 e5 6d 00 df 03 90
0000000274677930 > 00 00 00 00 00 00 00 00
0000000274677938   70 e2 c0 fa 01 00 00 00

video_pro_x.exe 04.10.2022 14:14 66d8a020

Memory Allocation
Base:       968
PE:       35.200
Pages:       13.107.200

PI:       477.568
PI_TEMP_DATA:   59.664
SI:       972.760
SI_TEMP_DATA:   108.456
FSI:       37.680

Blocks:       100.548
Temporary:   0
BE:       3.296.000
PLE:       1.355.364
BE Pool:       8.112
PLE Pool:       0
wHdr/inst:   1.768
Image Cache:   0
Video:       305.606.911(0/0)
Bitmap:       17.518.678

Thumbnail Cache:   73.635.698
SI Display Cache:   7.148.660
PLE Display Cache:   8.641.592

Buffer: 9.446.808
Pointer: 0

Title:       0
Memory GF:       0
Memory GF Zero:       0
Memory GF Zero_Dyn:       0
Memory GF Dyn:       0
Memory TT:       0
Audio Effect:       344
PPE:       60.000

Video Monitor:   0
malloc/free:   0
DIB:       15.654.012

VP: admin:       10.680
VP+Trans: privateData:       28.374
Transitions::       0

Frame Cache:   0
EXIF:       32
VSW:       0
DVDMAKER:   2.880
global UI (malloc):   0
global UI (valloc):   553.648.128
NOWAGGLE:   0
ReaderFrame:   1.455.676.443
MP3 Reader:   0
JPEG buffer:   0

Private Bytes: 10516 MByte

TLS:       926
MXGUI:       90.142.876
Sum:       2.558.818.668

Processor [46] 3600MHz 4 Core(s)
Microsoft Windows NT 10.0 (Build 19045)
Used Memory: 7944 MB Max Used Memory: 8162 MB
Free Virtual Memory: 28780 MB Total Virtual Memory: 131072 GB

Call stack:
Address Frame
0000000274677930 000000000014BA50 0000:00000000
00000001400CC49E 000000000014BAB0 QWinWidget::trUtf8+2E19E
00000001400CB72B 000000000014BAE0 QWinWidget::trUtf8+2D42B
000000014035A42D 000000000014BB60 boost::serialization::singleton_module::unlock+1262AD
00007FFF0E230E67 000000000014BCB0 MxQt::QObject::qt_static_metacall+1467
00007FFF0E23FA6C 000000000014BCF0 MxQt::QTimer::timeout+DC
00007FFF0E23859D 000000000014BF00 MxQt::QObject::event+8D
00007FFF0F4B49A0 000000000014BF30 MxQt::QApplicationPrivate::notify_helper+110
00007FFF0F4B3A23 000000000014C470 MxQt::QApplication::notify+18B3
00007FFF0E211B9A 000000000014C4E0 MxQt::QCoreApplication::notifyInternal2+BA
00007FFF0E25C4D9 000000000014C530 MxQt::QEventDispatcherWin32Private::sendTimerEvent+F9
00007FFF0E25A909 000000000014C580 MxQt::QEventDispatcherWin32::event+149
00007FFF0F4B49A0 000000000014C5B0 MxQt::QApplicationPrivate::notify_helper+110
00007FFF0F4B3A23 000000000014CAF0 MxQt::QApplication::notify+18B3
00007FFF0E211B9A 000000000014CB60 MxQt::QCoreApplication::notifyInternal2+BA
00007FFF0E213915 000000000014CC20 MxQt::QCoreApplicationPrivate::sendPostedEvents+215
00007FFF19CA377F 000000000014CC28 0001:0006277F C:\Program Files\MAGIX\ProX 14\Qt\Qt_x64\platforms\qwindows.dll
0000000108E7B400 000000000014CC30 0000:00000000
0000000100000000 000000000014CC38 0000:00000000
00000000095A53D0 000000000014CC40 0000:00000000
000000005A1A3FD0 000000000014CC48 0000:00000000

----------------------------------------------------------------------
MAGIX Video Pro X14 21.11.2022 15:14
----------------------------------------------------------------------
CrashDump 20221121_151453_v20.0.3.176.dmp successfully written

Error in module "video_pro_x.exe" (Load address: 0x0000000140000000) to address 0x00000001400CC538 (Exception 0xc0000005 "ACCESS_VIOLATION")

Main Thread   (ThreadID: 000031bc)
00000001400cc530   ff 50 50 eb 13 48 8b 01
00000001400cc538 > ff 90 00 03 00 00 a8 03
00000001400cc540   40 0f b6 f6 41 0f 44 f4

video_pro_x.exe 11.11.2022 11:21 fbd93bb0

Memory Allocation
Base:       968
PE:       35.200
Pages:       13.107.200

PI:       467.072
PI_TEMP_DATA:   49.720
SI:       942.288
SI_TEMP_DATA:   89.352
FSI:       37.680

Blocks:       100.584
Temporary:   0
BE:       3.264.000
PLE:       676.004
BE Pool:       6.096
PLE Pool:       0
wHdr/inst:   0
Image Cache:   0
Video:       2.451.470(0/0)
Bitmap:       1.290.530

Thumbnail Cache:   6.938.570
SI Display Cache:   992.992
PLE Display Cache:   407.004

Buffer: 0
Pointer: 0

Title:       0
Memory GF:       0
Memory GF Zero:       0
Memory GF Zero_Dyn:       0
Memory GF Dyn:       0
Memory TT:       0
Audio Effect:       200
PPE:       0

Video Monitor:   0
malloc/free:   0
DIB:       0

VP: admin:       10.320
VP+Trans: privateData:       28.310
Transitions::       0

Frame Cache:   0
EXIF:       0
VSW:       0
DVDMAKER:   2.880
global UI (malloc):   0
global UI (valloc):   100.663.296
NOWAGGLE:   0
ReaderFrame:   0
MP3 Reader:   0
JPEG buffer:   0

Private Bytes: 2330 MByte

TLS:       923
MXGUI:       87.641.964
Sum:       220.078.964

Processor [46] 3599MHz 4 Core(s)
Microsoft Windows NT 10.0 (Build 19045)
Used Memory: 1564 MB Max Used Memory: 1589 MB
Free Virtual Memory: 37302 MB Total Virtual Memory: 131072 GB

Call stack:
Address Frame
00000001400CC538 000000000014BAB0 QWinWidget::trUtf8+2E238
00000001400CB7CB 000000000014BAE0 QWinWidget::trUtf8+2D4CB
000000014035A58D 000000000014BB60 boost::serialization::singleton_module::unlock+12645D
00007FFF03590E67 000000000014BCB0 MxQt::QObject::qt_static_metacall+1467
00007FFF0359FA6C 000000000014BCF0 MxQt::QTimer::timeout+DC
00007FFF0359859D 000000000014BF00 MxQt::QObject::event+8D
00007FFF043A49A0 000000000014BF30 MxQt::QApplicationPrivate::notify_helper+110
00007FFF043A3A23 000000000014C470 MxQt::QApplication::notify+18B3
00007FFF03571B9A 000000000014C4E0 MxQt::QCoreApplication::notifyInternal2+BA
00007FFF035BC4D9 000000000014C530 MxQt::QEventDispatcherWin32Private::sendTimerEvent+F9
00007FFF035BA909 000000000014C580 MxQt::QEventDispatcherWin32::event+149
00007FFF043A49A0 000000000014C5B0 MxQt::QApplicationPrivate::notify_helper+110
00007FFF043A3A23 000000000014CAF0 MxQt::QApplication::notify+18B3
00007FFF03571B9A 000000000014CB60 MxQt::QCoreApplication::notifyInternal2+BA
00007FFF03573915 000000000014CC20 MxQt::QCoreApplicationPrivate::sendPostedEvents+215
00007FFF0535377F 000000000014CC28 0001:0006277F C:\Program Files\MAGIX\ProX 14\Qt\Qt_x64\platforms\qwindows.dll
000000005F04C600 000000000014CC30 0000:00000000
0000000100000000 000000000014CC38 0000:00000000 C:\Program Files\MAGIX\ProX 14\video_pro_x.exe
000000000A182A60 000000000014CC40 0000:00000000
000000005F259100 000000000014CC48 0000:00000000

Also why does the header say version 175 when the product version under help states as downloaded, version 20.0.3.1.176

Ray.

Marc-Goder wrote on 11/21/2022, 9:50 AM

What is "C:\Program Files\MAGIX\ProX 14\Qt\Qt_x64\platforms\qwindows.dll" ?

Can you still compare whether this file has changed to the previous version?

emmrecs wrote on 11/21/2022, 10:18 AM

Hi Andy.

Thanks for the heads-up on these updates to VPX 14 and MMS Suite 2023. Along with the reminder about the problem I reported with the earlier patch!

I assume this was the first time you had experienced this error? If so, it seems that I am not alone, since this latest patch also produced the error message in both apps for me. But, on starting them (following the message) both were actually patched to the latest version! Was this also true for you?

I think a support ticket may well be in order!

One positive change, which is listed in the list of changes, NeatVideo does now show in the KF editor and so can be deactivated without having to completely remove it. I need to check whether other third-party effects are also now shown in the KF editor.

Hi Ray

I'm not seeing the issue of instantiating the Limiter on the Master crashing the app (VPX 14). However, i do see that, on re-opening the project, the mixer Mastering light is still illuminated but the Limiter is not active! Selecting to re-activate it produces a "pause" in the playback sometimes occurring; all is clearly not well here!

Jeff

CubeAce wrote on 11/21/2022, 10:30 AM

Hi Mark.

I'm not that good with program error fault finding. I have no idea if anything has changed at that spot in the program or in fact what it is. Have never had that crash before.

@emmrecs

Hi Jeff.

I have no idea why this is happening but maybe because I'm running to many instances of plugins there is a memory address problem somewhere? No sign of maxing out any memory unless it is vram though.

Have been able to activate the limiter without causing a crash if I leave the panel open for 30 seconds before trying to apply the limiter. It is still forgotten on the next startup of the program.

I have also generated a new warning when this crash has now occurred for the fourth time.

Plus before the crash that brought that warning message.

Ray.

me_again wrote on 11/21/2022, 10:37 AM

@emmrecs

Greetings Jeff,

Yes, this is the first update for MS2023 for me. It didn't have time to update anything, as soon as I clicked on the uodate button that screen came up so still on 165.

The only problem now is that every time I load up MS2023 the update screen pops up. When I click on launch previous program version it pops up again. I don't want to cancel the window completly for obvious windows so hopefully this will be sorted soon.

I raised a ticket as soon as I'd finished posting here.

AndyW

emmrecs wrote on 11/21/2022, 10:41 AM

Hi Andy,

Interesting! So, for you the message appears even before the actual update process has started? Is that correct? If so, your situation is clearly different to mine. For me, the message appears after the update has "installed"; hence, I am able to open the app and see that is has, actually, updated.

When you created the ticket did you reference this thread in the forum?

Jeff

me_again wrote on 11/21/2022, 10:56 AM

@emmrecs

When you created the ticket did you reference this thread in the forum?

No, but I have now on the ticket they supplied.

AndyW

johnebaker wrote on 11/21/2022, 12:21 PM

Hi Ray

. . . . Also why does the header say version 175 when the product version under help states as downloaded . . . .

It is an old dump file - look at the time the dump was created:

MAGIX Video Pro X14 20.11.2022 00:50

You were still on .175 then.

When posting a dump log most of the information is superfluous - the important bits for us are:

MAGIX Video Pro X14 21.11.2022 15:14
----------------------------------------------------------------------
CrashDump 20221121_151453_v20.0.3.176.dmp successfully written

Error in module "video_pro_x.exe" (Load address: 0x0000000140000000) to address 0x00000001400CC538 (Exception 0xc0000005 "ACCESS_VIOLATION")

Call stack:
Address Frame
00000001400CC538 000000000014BAB0 QWinWidget::trUtf8+2E238
00000001400CB7CB 000000000014BAE0 QWinWidget::trUtf8+2D4CB
000000014035A58D 000000000014BB60 boost::serialization::singleton_module::unlock+12645D
00007FFF03590E67 000000000014BCB0 MxQt::QObject::qt_static_metacall+1467
00007FFF0359FA6C 000000000014BCF0 MxQt::QTimer::timeout+DC
00007FFF0359859D 000000000014BF00 MxQt::QObject::event+8D
00007FFF043A49A0 000000000014BF30 MxQt::QApplicationPrivate::notify_helper+110
00007FFF043A3A23 000000000014C470 MxQt::QApplication::notify+18B3
00007FFF03571B9A 000000000014C4E0 MxQt::QCoreApplication::notifyInternal2+BA
00007FFF035BC4D9 000000000014C530 MxQt::QEventDispatcherWin32Private::sendTimerEvent+F9
00007FFF035BA909 000000000014C580 MxQt::QEventDispatcherWin32::event+149
00007FFF043A49A0 000000000014C5B0 MxQt::QApplicationPrivate::notify_helper+110
00007FFF043A3A23 000000000014CAF0 MxQt::QApplication::notify+18B3
00007FFF03571B9A 000000000014CB60 MxQt::QCoreApplication::notifyInternal2+BA
00007FFF03573915 000000000014CC20 MxQt::QCoreApplicationPrivate::sendPostedEvents+215
00007FFF0535377F 000000000014CC28 0001:0006277F C:\Program Files\MAGIX\ProX 14\Qt\Qt_x64\platforms\qwindows.dll
000000005F04C600 000000000014CC30 0000:00000000
0000000100000000 000000000014CC38 0000:00000000 C:\Program Files\MAGIX\ProX 14\video_pro_x.exe
000000000A182A60 000000000014CC40 0000:00000000
000000005F259100 000000000014CC48 0000:00000000

John EB

johnebaker wrote on 11/21/2022, 12:38 PM

. . . . What is "C:\Program Files\MAGIX\ProX 14\Qt\Qt_x64\platforms\qwindows.dll" ? . . . .

It is part of the Qt software and design development tools suite. Many programs are created using this instead of, or in addition, to Microsoft Visual Studio.

As the file is platform specific it is most likely to contain routines that enable Qt to interface with the Windows C++ environment.

John EB

CubeAce wrote on 11/21/2022, 2:46 PM

@johnebaker

Hi John.

That report I posted was on the second time it crashed after the update. After that I did a restart of the PC but I can still mange to crash the program. Most of it seems sluggish. I can't move the program to the other monitor easily or at once. Nor any of the two editing monitors. If I grab one the first attempt always fails. If I then don't attempt to do anything for a further 20 seconds I can grab the monitor as usual with the mouse and move it. It doesn't matter what combination of GPU CPU settings I use. Since the update, some combinations of GPU use have sent memory usage through the roof.

Exports have actually got longer in VPX 14 since the update and MEP 2022 was already thrashing VPX in that department as well. Only one thing seems to have improved for me. That is now selecting my nvidia card for all processes does not result in an export suddenly just freezing to a halt or shutting the program down.

Now, with no effects running, the export times are faster but still slow down quite a bit on visual cross-fades which seem to be handled solely via the CPU. Choosing all nvidia for hardware acceleration seems to have locked out the use of the HD 630 completely for any 3D work, not like earlier versions of VPX. I haven't dared try Microsoft WARP again. I have also never seen my nvidia card grab 13GB of reserved system graphics memory before VPX14 either.

Ray.

me_again wrote on 11/23/2022, 2:23 AM

Morning all,

Still no joy with this update and so far no reply from Magix, so this morning I thought I'd try an external manual update using the patch exe; I've done this succesful;ly before.

When I look in the "normal" place for the update file, the folder is empty even while the file is alledgedly downloading:-

This raises two questions:

Is the temporary download location in a different place in MS 2023?
Has anyone else successfully used this update or is it just my system that doesn't like it?

AndyW

CubeAce wrote on 11/23/2022, 2:50 AM

Hi Andy. I had no trouble with the update. Didn't even have to turn off any AV.

My advice though is don't.

VPX 14 has become virtually unusable on my machine since. Now I'm getting audio problems as well. A clip will start off well enough and eventually degenerates in something sounding like a Dalek while while the memory commit charge is increasing beyond the 32 GB of memory I have. The export time of my 47 minute project has increased by another ten minutes if it doesn't crash before finishing. Playback is joke. Write to disk tops out at around 27MB/s in VPX 14 compared to MEP 2022 at up to 127MB/s. In VPX 14 my nvidia card is trying to grab more system reserved Shared GPU memory (13GBs +) than my CPU can manage.

There is also something different in the way the files are being encoded when exported. For the exact same settings MP4 settings I'm getting 10 to 15% more compression in the file from using the same project file between MEP 2022 and VPX 14 though that was true before the update. MEP 2022 is breezing through the project while VPX 14 is making a dogs dinner out of it. I'm sure if I only had one track running with no effects the program would be running just fine but Magix should in my 'not so humble opinion at this increasingly frustrating point' make more of a disclaimer about the minimum running requirements for this generation of Magix video editing software. Their Facebook and twitter accounts are getting more stick than here and all Magix is replying is they don't take kindly to abusive posts.

At least I don't have a 365 account and have the choice of rolling back to a working version. 😅

Ray.

johnebaker wrote on 11/23/2022, 3:30 AM

Hi Andy

Like @CubeAce i had no issue with the Update.

. . . . Windows 11 but Smart App Control is greyed out i.e. when I search for it then click on it absolutely nothing happens. I assume this is because I have Norton 360 installed.

Smart App control is independent and should not be affected by which antivirus program you have installed.

However if you upgraded to Windows 11 from 10 then Smart App Control may not be activated.

. . . . It's a good program but it does like it's own way. . . . .

I think the ' liking its own way' may qualify for the 'Understatement of the Year Award' 😂, you are not kidding! The 'good' I will not comment on .

John EB

AAProds wrote on 11/23/2022, 4:10 AM

Ray, I stand to be corrected but topic is for an update to MMS 2023. You seem to be talking about an update to VPX 14.

CubeAce wrote on 11/23/2022, 4:49 AM

Hi Al.

Agreed, but both had the same update package and both are having the same problems associated with them, hardware differences depending.

Ray.

AAProds wrote on 11/23/2022, 5:19 AM

Ray, OK, fair enough.

MEP 2022 is breezing through the project while VPX 14 is making a dogs dinner out of it. I'm sure if I only had one track running with no effects the program would be running just fine but Magix should in my 'not so humble opinion at this increasingly frustrating point' make more of a disclaimer about the minimum running requirements for this generation of Magix video editing software.

If what you say is true, it's less the hardware requirements (that didn't actually change from 2022 to 2023) and more bad programming. If 2022 works OK, then the very next version cannot possibly be so demanding on gear that it starts behaving like a pork chop. They've just messed up the code, that's all.

Anyway, it seems nobody's complaining about the actual performance, only the install. You done that re-format yet? 🙂

CubeAce wrote on 11/23/2022, 6:15 AM

Hi Al.

How often do you reformat? It would take me a week or more of getting the programs I use to work the way I use them. I bet when I eventually give up on VPX 14 and re-install VPX 12 that that version behaves as it did before.

I keep on top of things like broken registry entries and garbage left over dump and temp files. I have scanned for faults. Plus it would not just be my C: drive but the clone C: drive as well.

Are you not seeing patterns of complaints yet with the same symptoms for both programs when either an older than 10th gen Intel CPU is in use with or without a inboard GPU plus a nvidia card? Even if that nvidia card is a 3000 series and has more than 4GB of vram.

Why has the amount of ram being used more than trebled in any situation?

Why does adjusting the sound buffers not clearing audio stutter at all now?

Why have Magix added that using the zoom position rotation effect now effects performance since this update?

Why when using the same project using the same export parameters, does VPX produce a file that is more compressed than my copy from MEP 2022? That has never happened with any of my past two versions of VPX.

Those are my results from my typical rendering settings. Yes they are not normal but past versions have doped well.

MEP export time. Average

VPX 14 Export time. Best

There are other 'idiosyncrasies' as well.

I'm not saying the programs are completely balked and may well be working as they should with the correct hardware. It's just the amount of 'correct hardware' for all but the most basic of editing has suddenly shrunk a great deal. That I feel is where Magix is doing a disservice, yet again, only telling us the good stuff. You should look at the Magix twitter feed. In fact, it you take away performance differences as they quote them, what significant differences does the program actually give us that we can't live without? Even the playback smoother rhetoric only seems to apply to those either doing simpler less demanding things or had much newer hardware.

Ray.

Marc-Goder wrote on 11/23/2022, 6:18 AM

Anyway, it seems nobody's complaining about the actual performance, only the install. You done that re-format yet? 🙂

https://www.magix.info/de/forum/exportzeiten-sehr-lang-in-version-2023--1309436/?page=2

Look there

AAProds wrote on 11/23/2022, 7:19 AM

How often do you reformat?

I have conniptions thinking about it! I'm slowly making up my new machine but am doing so reluctantly! 😂

I've customised by Win 10 setup to the billyoh and I am dreading setting it up again on the new box.

That said, the pure and utter joy of using a brand new install of Windows makes up for all of the heartache.

If I had your setup, I'd image it, then wipe and re-install just to see if Magix really is a dog's breakfast. You can always roll-back to the previous setup.

The other points you raise are, in my view, mostly caused by bad software code. If it needs Artemis components to run complex projects, then Magix should fess up and tell us. The majority of you guys have far exceeded the system "requirements" and shouldn't be having trouble. And Magix shouldn't be putting out stuff that crashes simply because you've got the Hardware Accel settings incorrectly set.

Not sure of the relevance of that topic, Marc. All it shows is that all the iGPUs are dogs compared to proper GPUs, which is well-known from the GPU comparison tests on the internet. Mind you, I'd like some of those export times please! Coming with my new machine, hopefully.

I liked this comment:

Retrofitting the PC with an Nvidia GPU would now also be worthwhile for 4K video.

They don't say! 😊

johnebaker wrote on 11/23/2022, 8:06 AM

@AAProds, @CubeAce, @Marc-Goder

. . . . They've just messed up the code, that's all. . . . .

Something is definitely messed up - I am getting export times ~45% longer (VPX 14), for both 4K UHD and FullHD exports from the 4K project , cannot test MMS 2023 as the project movies are using features from VPX not in MMS 2023.

John EB

CubeAce wrote on 11/23/2022, 8:07 AM