@johnebaker

Greetings John,

Instability issues? Not in the way I understand instability. However there has always been (with MS2023) an anomaly when I put the computer to sleep for a while with MS loaded and running a project.

When I wake the computer, on occasion MS would appear but the timeline and everything associated with it was not there. When I moved the cursor over where the "bits" should be they appeared and were usable.

It was not really a problem and I just put it down to being another Magix quirk. This morning I've made the computer sleep and wake far more than I normally would in 2 hours and all now seems to work OK so maybe that's been fixed in this patch.

As for anything else it's a little too early to tell really.

AndyW

In the German forum there are reports about renewed problems after the new update.

NewBlue Color Replace filter or Film Color 2, etc. They no longer work at all via the GPU.  Pro X14 hangs and you can only kill it via Task Manager.  Version 20.0.3.180 ran flawlessly.

@johnebaker @me_again

Hi Andy.

Nothing I've tried to report is fixed like the problems of various settings not being applied on reopening a project.

At the same time I can't replicate any of the problems @Marc-Goder has reported from the German forum.

Ray.

@johnebaker @johnebaker @Marc-Goder

At the moment I agree with Ray in that the NewBlue effects seem to work OK in MS2023.

The really good news for me is that ProDAD have released an update to Mercalli Pro V6 and it now works as it should. I've posted about this https://www.magix.info/us/forum/mercalli-pro-v6-plug-in-offer-bug--1312964/?page=2

AndyW

@me_again

Mercalli Pro V6 Update gets positive approval everywhere and everyone reports improvements.

@Marc-Goder @me_again @johnebaker

I'm going to retract everything I said earlier regarding the NewBlue Color Replace filter.

I used it more thoroughly and it caused VPX 14 to crash but I could not send a crash report to Magix after. I kept getting the cannot connect message.

Here is the crash report.

----------------------------------------------------------------------
MAGIX Video Pro X14  17.03.2023  11:29
----------------------------------------------------------------------
CrashDump 20230317_112927_v20.0.3.181.dmp successfully written

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

Main Thread   (ThreadID: 000033d8)
  00000001401a852f   81 00 90 48 8b 4c 24 60
  00000001401a8537 > 48 8b 01 ff 50 60 84 c0
  00000001401a853f   0f 84 17 01 00 00 48 8b

video_pro_x.exe    06.03.2023  17:22      247909e0

Memory Allocation
Base:        968
PE:        35.200
Pages:        13.107.200

PI:        81.344
PI_TEMP_DATA:    49.720
SI:        389.104
SI_TEMP_DATA:    48.000
FSI:        1.920
Blocks:        4.916
Temporary:    0
BE:        160.000
PLE:        676.724
BE Pool:        528
PLE Pool:        0
wHdr/inst:    544
Image Cache:    0
Video:        45.242.215(0/0)
Bitmap:        1.109.091

Thumbnail Cache:    24.917.190
SI Display Cache:    2.086.080
PLE Display Cache:    584.724

Buffer:        1.189.608
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:        232
PPE:        40.000

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

VP: admin:        4.200
VP+Trans: privateData:        789.219
Transitions::        0

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

Private Bytes:    4668 MByte

TLS:        968
MXGUI:        106.479.500
Sum:        348.146.803

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

 Call stack:
Address   Frame
00000001401A8537  000000000014C560  boost::archive::codecvt_null<wchar_t>::do_encoding+9A1D7
00000001409DB9C5  000000000014C590  QWinWidget::show+325605
00007FFE0429727C  000000000014C5E0  0001:001E627C C:\WINDOWS\SYSTEM32\mfc140u.dll
00007FFE042C13D2  000000000014C620  0001:002103D2 C:\WINDOWS\SYSTEM32\mfc140u.dll
00007FFE04349885  000000000014C6B0  0001:00298885 C:\WINDOWS\SYSTEM32\mfc140u.dll
00007FFE04348960  000000000014C830  0001:00297960 C:\WINDOWS\SYSTEM32\mfc140u.dll
00007FFE043488BF  000000000014C870  0001:002978BF C:\WINDOWS\SYSTEM32\mfc140u.dll
0000000140A9F5D0  000000000014C8D0  QWinWidget::show+3E9210
00007FFE0434615E  000000000014C9C0  0001:0029515E C:\WINDOWS\SYSTEM32\mfc140u.dll
00007FFE04346524  000000000014CA00  0001:00295524 C:\WINDOWS\SYSTEM32\mfc140u.dll
00007FFE041E96E9  000000000014CA40  0001:001386E9 C:\WINDOWS\SYSTEM32\mfc140u.dll
00007FFE5D65E7E8  000000000014CBD0  CallWindowProcW+3F8
00007FFE5D65E229  000000000014CC50  DispatchMessageW+259
00007FFE0483B09C  000000000014FD80  MxQt::QEventDispatcherWin32::processEvents+59C
00007FFE2B5D3759  000000000014FD88  0001:00062759 C:\Program Files\MAGIX\ProX 14\Qt\Qt_x64\platforms\qwindows.dll
0000000009F7EBC0  000000000014FD90  0000:00000000

Further more, letting the computer sleep while the program was open but not playing, resulted in Windows not awakening my Intel powered monitor where the main program was residing. It remained blank.

The effect itself is behaving badly as if it is not using memory correctly.

Key frame editor does not show the effect as being in use upon re-opening the program unless I go to the effect itself in the effects section and click on it once.

Ray.