@CubeAce

Nothing appears. Sending the cash log to Magix does work - or at least it says its been sent, but actually viewing the log by pressing the button doesn't work on my system although I know the log exists.

Post note: I deleted the contents of the Crash directory thinking that would resolve the issue. Crashed the system (I found a bug that consistently freezes the startup) and noted that the Crash directory repopulated successfully but I still am not able to view the log report from the crash window.

@Can-Dive

Have you looked at the Windows event viewer to see if there is any information there?

Local Disk (C) Windows / system32 / eventvwr.exe

Ray.

@CubeAce

Hi Ray,

You might want to check your spelling in your latest post!! (Just to ensure no-one is "offended" by that one-letter difference!) I could edit your post but thought it best to allow you the privilege.

Jeff

@Can-Dive

Hi

. . . . actually viewing the log by pressing the button doesn't work on my system although I know the log exists . . . .

This is probably Windows Explorer in a hung state, so the open log action fails.

Two thingways to get out of this are:

• Press Ctrl+Alt+Delete to bring up the logoff.switch user/shutdown dialog, then cancel it by pressing the Esc key.
   
• Perform a full restart of the computer, not a normal shutdown/power up.

HTH

John EB

@emmrecs

Sorry Jeff I'm too late. 😢

Ray.

@CubeAce

No problem Ray.

As you can see, I have now edited the original!

Jeff

@CubeAce, I took a look at the event viewer and learned more about the bug I found than why I can't open the Crash Log.

@johnebaker, I tried your two suggestions but I still could not open the Crash Log from within the popup window.

The problem with my request to this forum is you need to crash the system to generate the Crash Log popup window so that you can press the display button to see the Crash Log (if it appears).

I'll explain how to crash your system so maybe we can kill two birds with one stone. It's pretty simple. I'm using Windows 11.

1. With VPX16 open, go to the Window menu and untick Program monitor.
2. Close the program
3. Start the program. The splash screen will freeze with the following error message sitting behind the splash screen (see below)
4. Kill VPX16 via the Task manager.
5. The only way to restart VPX16 is to delete the Video_Pro_X16.ini file in AppData
6. When the system restarts, the Crash Log popup window will appear.
7. Press the display button to determine if the Crash Log displays.

Following the above procedure will help me determine first, if the VPX16 start up freeze only happens to me or is widespread. Note; MMS 2024 on the same machine and VPX 11 on another machine running Win10 reopened without incident.

Second, generating the Crash report popup window will help me determine if pressing the display button will show the Crash Log or not. If it does then there is obviously something wrong with my system.

Thanks for all your help - Cheers!

@Can-Dive

Can I suggest an initial step in your process, in order to ensure that any customised settings for VPX16 are not lost?

1. Make a copy of the Video_Pro_X16.ini file from AppData and save it somewhere other than your AppData folder, perhaps to a different drive if you have one.

2. Proceed as per @Can-Dive's post.

3. Once completed, close VPX, go to and delete the newly-created .ini file. Move the previously-saved version of your .ini file back to the appropriate AppData folder. This should ensure your installation of VPX16 returns to how it was before!

Jeff

@Can-Dive

Hi

. . . . if the VPX16 start up freeze only happens to me or is widespread . . . .

Deleting the Program Monitor will cause a crash every time.

IMO this is a bug, either the option to remove it should not be there, or is recreated/enabled on restart.

For completeness, it does not matter whether the Source monitor it is deleted or not, the Pogram Monitor is a key compnent of the interface.

AFAICS, VPX knows it ihas crashed, the log is created however crash.ini does not appear to be updated.

John EB

@emmrecs, good recommendation!

@johnebaker, unticking Program Monitor didn't crash VPX11 so something has changed over time. I don't think unticking the Program Monitor or any other window within the program actually shuts down the window. While the Program Monitor isn't visible, it's still "present" in memory (or should be). When the system restarts, the Program Monitor restarts; it's just hidden.

While the Program Monitor is important, it isn't during the initial stage of my workflow of making rough cuts and placing them into the Project File. Below is the custom window I use to make these initial cuts. I usually set a "trim scene" of 5 - 10 seconds in duration and scrub this block along (Ctrl + left click drag of the mouse). A single clip may have a number of scenes I want to move to the Project Folder. The size of the display window makes it easier to trim the video and there is a natural left to right workflow. Once all the scenes are in the Project Folder, I use another custom window to select/cull and move the scenes to the timeline

Now I have just discovered that if I untick the Source Monitor, the Program Monitor takes on the characteristics of the Source Monitor! So I could set up the exact same workspace with the Program Monitor acting as the Source Monitor. Further testing is required...

AFAICS, VPX knows it ihas crashed, the log is created however crash.ini does not appear to be updated.

I'm not sure what you mean? Does the Crash log open, when you press the display button?

@johnebaker @emmrecs @CubeAce

Further testing completed.

I have confirmed that both MMS 2024 and VPX11 do not suffer from this bug meaning that you can untick the Program Monitor to "hide" it, close the program and reopen it without issue. So the Program Monitor does not have to be active for the system to run.

With further testing, I have discovered that the problem is not the Program Monitor but the Source Monitor.

Conduct the following steps:

1. With VPX16 open, go to the Window menu and untick the Program Monitor and untick the Source Monitor.
2. Close the program
3. Start the program. VPX16 will start without incident and only the Media Pool, Project window and Project folder will be visible (as expected)
4. Go to the Window menu and tick the Program Monitor. It appears.
5. Tick the Source Monitor. It appears.

Everything works as expected.

Now follow the exact same steps as above but in step 4; tick the Source Monitor first.

The system crashes

Findings and next steps

I believe this bug was introduced in VPX16. I suspect it also exits in MMS2025 but I don't have it to test.

I believe this bug does not exist in versions prior to VPX16/MMS2025. I know it doesn't exist in MMS2024 and VPX11 so I'm assuming VPX15 and prior versions are ok as well as MMS2024 and prior versions.

If forum members who have the current versions or prior versions can confirm my findings, that would be great! I'll then submit a bug report to Support.

I still cannot open the Crash Report in VPX16 - this may or may not be related.

Cheers

@Can-Dive

I know it doesn't exist in MMS2024

Movie Studio doesn't have a second monitor (whatever you want to call it 😉). MMS2025 runs fine when switching "the" monitor on and off.

Why, in VPX, would you want to operate without the source monitor?

Obviously the program shouldn't crash here but is it really a issue that will take up valuable programming time to fix?

@Can-Dive

Hi,

I have to agree with Al, but would just add - why would you turn off both monitors and exit the program? And then turn on the Source monitor first? Pretty obscure bug IMO.

Given the circumstances with Magix, I would just concentrate on getting them to fix the more obvious bugs, like the PTF 1 second problem, and SF Audio Cleaning Lab not working properly with VPX.

On my YT channel, there have only been 89 views for the PTF problem, but 2,345 views for the SFACL bugs.

John CB

@AAProds

Hi Al

. . . . Why, in VPX, would you want to operate without the source monitor? . . . .

Sometimes it is a necessity, I do this regularly, when I am working on my laptop, as now, and I do not have access to a second monitor, eg a TV. to use as a second monitor.

As I previously commented, being able to turn the Source (Media Pool) monitor off/on is not an issue for working with the program, and is not an absolute requirement. Some users prefer to use this for selecting media using In/Out points, however you can do without it.

Having the ability to turn off the Program monitor is, IMHO, a definite no no.

When the Source monitor is turned off, the Program (Timeline) monitor, behaves the same as MMS 2025, including previewing media from the media pool and setting In/Out points for adding to the timeline.

John EB

@AAProds

MMS2025 runs fine when switching "the" monitor on and off.

Thanks for confirming. Now I know the bug is with the Source Monitor in VPX16; not the Program Monitor.
 

Why, in VPX, would you want to operate without the source monitor?

This is a great question and as @johnebaker has indicated, the two monitors take up too much screen real estate if you are working on a laptop. The great feature of the Program Monitor is that it can act as both Source and Project Monitor. So, in VPX you can have the same look and feel as MMS with the added bonus of the Project file.

@browj2

why would you turn off both monitors and exit the program? And then turn on the Source monitor first? Pretty obscure bug IMO.

You are missing the point of the exercise. As per the OP, I need someone to confirm that in VPX16 they cannot open the Crash Log. To test this, one needs to crash the system first. This is a way of doing it.

Since you have VPX16, would you do me a big favour? Follow the steps to crash the system and let me know if you can/cannot access the Crash Log via the popup window when you restart the system. Once confirmed, I'll report both bugs to Support.

Given the circumstances with Magix, I would just concentrate on getting them to fix the more obvious bugs, like the PTF 1 second problem, and SF Audio Cleaning Lab not working properly with VPX.

I agree with you 100% but, we have no control over how the Development team will prioritise bug fixes. All we can do is report them so they are aware of the issues.

How long has the PTF 1 second problem been outstanding VPX15, 14, 13? I know it doesn't exist in VPX11.

As for SF Audio Cleaning Lab, I again agree. The 101 error is so frequent that I stopped using the software in frustration.  But unfortunately, in my opinion, SFACL is a deprecated product. Magix responded to you in the following post and basically told you so in nicer words.
https://www.magix.info/us/forum/new-update-is-available-for-samplitude-pro-x8-and-pro-x8-suite--1340950/#ca1950041

@browj2 Thank you for your feedback and suggestions for the Cleaning Lab. I have passed on the notes. We have already documented the problems. At the moment, the software is in dormant “legacy” mode and we cannot foresee when capacities can be released for renewed maintenance of the product.

Your reply to them regarding reputational damage is valid. If the software is truly deprecated and they do not plan to fix it, then they should stop selling it and perhaps offer version 4 owners an opportunity to download version 3 since this seems to be the last 64 bit version to work properly (or a provide a refund).

@johnebaker

Having the ability to turn off the Program monitor is, IMHO, a definite no no.

I respectfully disagree. Turning off the program monitor works in the latest version of MMS. it also works in VPX16 but it's the Source Monitor that is causing the freeze issues. I have a number of custom windows; one for rough cuts, another specifically for Effects and a third that maximises the project timeline. I also created one called "Hub" which is essentially one big window for the Hub so I can select and preview the media available. I don't need or want the Program Monitor turned on in this case.

@Can-Dive

Hi,

You are missing the point of the exercise. As per the OP, I need someone to confirm that in VPX16 they cannot open the Crash Log. To test this, one needs to crash the system first.

Sorry, I forgot to mention that I did try it, it crashed and I was able to and did send in a crash report. I put in a link to this thread in the text of the crash report.

Turning off the program monitor works in the latest version of MMS. it also works in VPX16 but it's the Source Monitor that is causing the freeze issues. I have a number of custom windows; one for rough cuts, another specifically for Effects and a third that maximises the project timeline. I also created one called "Hub" which is essentially one big window for the Hub so I can select and preview the media available. I don't need or want the Program Monitor turned on in this case.

There is a command for maximizing the 2 monitors - Alt+Enter or simply double-click on one or the other. There is an entry in the shortcuts that allows you to add a shortcut to switch whichever window has focus, to full screen. I have mine set to à. This would be better than creating a window arrangement. So to get the Media Pool (and Hub) full screen, create and use a shortcut.

As for SFACL, I and many others complained about the 101 error shortly after it first came out. First time round, I was told that the team was now working on Samplitude and would not be going back to SFACL to fix any bugs. Pitiful.

I have pointed out to Magix that they are still selling products with flagrant bugs and to not tell me that they are legacy or dormant when bugs were pointed out right after the programs were issued. You still sell it, so you still have to support it. SFACL and Photo Manager are the two culprits. Does anyone at Magix actually know what they have and how useful they are...when they work properly?

Even with the 101 and other bugs, SFACL is still an excellent program. There is nothing else, short of getting Samplitude, that has the Spectral Cleaning tool, not even the famous Sound Forge Pro (Spectralayers is a plugin and doesn't count). This is about the only tool available at a reasonable price to remove short glitches from audio.

The other thing is that when you use an effect, you can go back and change or remove it, or turn it off and on. In SF Pro, if you use any of the fx buttons that are on the screen, the effect is applied when you move on and you can't go back and change it later, at least, I can't figure out how to do it. I should add that ACL is and has always been the recommended upgrade to Music Editor 3 in the video programs. It used to work with them, should work with them, but doesn't. SFACL did. It should not be difficult to fix what used to work.

The PTF error came up in VPX15 - it worked fine in VPX14. This error was actually on any trimmed clips brought in from the Source Monitor directly to the PTF - in VPX14. It was fixed in VPX15 but they broke the same feature when sending clips, trimmed or otherwise, from the timeline. So, all they did was transfer the problem. This is ridiculous.

John CB

@Can-Dive

I should have mentioned that the full-screen shortcut is actually the small square at the top right of each of the windows that takes you to full-screen and back.

John CB

@browj2

I should have mentioned that the full-screen shortcut is actually the small square at the top right of each of the windows that takes you to full-screen and back.

Thanks for the tip, I'll employ it going forward. 👍🙂

Sorry, I forgot to mention that I did try it, it crashed and I was able to and did send in a crash report. I put in a link to this thread in the text of the crash report.

I too am able to send the crash log to Magix Support.

My problem is, on my computer, I cannot actually view the crash log. That button does not work for me. Can you press the button and see the details of the crash log?

@browj2, sorry for being pedantic. The reason being, If you can't open the crash log then that implies there may be a bug in the system. But if you can open the crash log and view it, then the problem is probably my system and not the VPX program. I don't want to falsely report a bug to Support if in fact the problem is my computer, my Window's configuration or something other than VPX/MMS. That is why I'm seeking someone to confirm my finding. If you can open the crash log by pressing the button then I have to go back to the drawing board to determine why it doesn't work on my computer.

Thanks for all your help!🤓

@Bol

Thank you for the confirmation!

Cheers,

Post note; it does work in VPX11 🙂