Unfortunately, not really. I had same problem first but I found an older Ignite 1.1 demo version caused the crash during VMS14 start. Deinstalling Ignite helped in my case.

When sending crash reports be sure not just using the "Send" button but creating a dump file by clicking "Send" while holding "Strg+Shift" and sending this dump file separately, just liked described in this post.

"3. Not possible to make advanced or customized settings in “Make Movie”."

I see what you mean in your screenrecording. The Render button is missing on your system. It's available on mine, though.

Do you have modified the font display size in your Windows system settings?

For your multicam problem: You first have to select "Create Multicam-Track". And this again only works if you selected the involved video tracks only, without the audio tracks.

Cornico.  I am experiencing the same problem as you mine is set at 125%.  Can you elaborate on how to manually address this please? My eyes are also nearly 70 years old 🤓 

Thinking about this, surely its up to Magix to address this issue rather that the user.  John

We have reproduced the issue with the render dialog here. We will work on a fix for this. In the short term, you can, in most cases, use the enter key to engage the render and close the dialog, or hit escape to cancel out of it.

Cornico, I have m2ts files from a Panasonic HDC-SD1 (5.1 audio). Dragging the file from the Vegas Explorer window yields the following error message, "The file xxxxxxx.m2ts could not be opened.  The file contains an unsupported number of channels (6)." I get the same error message in projects that are 2 channels or 5.1. It is worth noting that since VMS 9-13 those files never imported perfectly into the timeline with stereo audio as one channel audio always appeared to be much higher than the other. It had been reported as a bug back then. They worked fine being dragged into 5.1 projects (through VMS13). Now they don't work at all.

@Marco. and @VEGASDerek - please contact me if you want a sample to test or any other information. Happy to help!

@Cornico Nice workaround! I have VMS 12. I can confirm that the workaround works with v12 as well.

Thanks MAgixDerek. Yup hitting enter is fine as fix for the moment

4. Multitrack problems. For only two tracks I’m able to choose “Create Multitrack”. With 3 or more tracks that option is not available.

 

1.Select all video tracks you want. (Ctrl+select video tracks)

2.Select: Tools>Multicamera>Create Multicamera tracks

We have reproduced the issue with the render dialog here. We will work on a fix for this.

👍👍

Did anyone give an ETA on a fix?

Did anyone give an ETA on a fix?

This was the last word on the next update: https://www.vegascreativesoftware.info/us/forum/was-disable-resample-removed-from-movie-studio-platinum-14-0--105694/#ca654954

Active take information is still hardly readable or better said still unreadable....how long do we have to wait now...?

Hi guys, where have you found this build. I cannot find any notification of it and MS14 net notify still says 105 is the latest?

The did not say to fix it but to put it on (a?) to-do list.

What's the difference?

The[y] did not say to fix it but to put it on (a?) to-do list.

I guess we'll have to wait for that as well till v 15 as they "hope to provide a few different options for the interface color/brightness of Vegas 15. (These options will not be available yet in Movie Studio 14.)" I think I will.

The[y] did not say to fix it but to put it on (a?) to-do list.

I guess we'll have to wait for that as well till v 15 as they "hope to provide a few different options for the interface color/brightness of Vegas 15. (These options will not be available yet in Movie Studio 14.)" I think I will.

I´m not asking for a customizable interface color/brightness option, I just wanna be able to read the active take information, as I was able to read it in all other MS versions before! I cannot imagine that it is a big effort to change the color of a text string from light grey to black.

The same goes for the ruler times along the top of the timeline. They are dark grey against dark, dark grey and difficult to see. And it's still hard to see whether an icon is selected or not. Maybe the guys who design the UI have cat's nightime vision!

@3Point, as Cornico said, "No idea, maybe they can tell you" about that as well. The PO did say in another comment that "I wish that such fixes were as "simple" as you suggest." As for the GUI, it's my personal problem, I'm glad it's not yours. I agree very much with EricLNZ's comment above.

I'm afraid a fix for the various timeline contrast issues was not able to make it into the code before this update. It is near the top of our list for the next update.

For vkmast...I understand the pain with not having the adjustable interface. Due to the complexity of this improvement, it is very unlikely we will be able to put it into an update for VMS 14. We are currently still working on it for Vegas at the moment and it will likely take us up to the release of Vegas 15 before it is really complete. When it is complete, it can be turned on for VMS 15 as we develop that product release.

Your clarification is very much appreciated, Derek. That's what I've understood from your previous comments as well. Thank you. You just may have motivated me to get MVMSP 14 to support the development for my small part even if I might never use that version.