Open vf file with MS17. First scene zooms and pans around a jpg.
Open file with MS2023. Scene does not pan or zoom.
Hi
I assume your earlier post, re the crash, is resolved as you are able to import the MS 17 project.
. . . . Open file with MS2023. Scene does not pan or zoom . . . .
That is as expected.
In a nutshell, with the Vegas Creative Software division dropping further development of VMS after version 17 about 18 months ago, Magix, filled the product gap with a variant of Movie Edit Pro which could import basic edits only from older MS projects - no effects etc are imported as the 2 programs effects etc are not cross compatible.
Since January this year the Movie Edit Pro has been rebranded as Magix Movie Studio.
I would suggest you complete the project in VMS 17 if possible, otherwise any effects etc you had in the old project will have to be recreated in MMS 2023
To familiarise yourself with MMS effects etc see the tutorials by @browj2 here
Alternatively, you may want to consider changing to Vegas Edit to maintain compatibility and have the same workflow as in VMS, depending on when you purchased MMS 2023, you may be able to get a refund and upgrade price for Vegas Edit as you already have VMS.
HTH
John EB
Forum Moderator
I don't understand what you mean by "I assume your earlier post, re the crash, is resolved as you are able to import the MS 17 project." The crash was not resolved. It still crashes exactly as describe in my earlier post.
I was not aware that MS 2023 could not open previous versions.
Hi
. . . . I don't understand what you mean by "I assume your earlier post, re the crash, is resolved as you are able to import the MS 17 project." . . . .
From your previous post: . . . .File/Open vf project that worked with MS17 Platinum. It crashes. . . .
From this post which was made after the first post . . . .Open file with MS2023. Scene does not pan or zoom. . . . .
This indictates that if you are getting the project file loaded, however the effects from VMS are not present, this therefore would suggest the program is not crashing on loading the file.
. . . . I was not aware that MS 2023 could not open previous versions. . . . .
It can, as I described previously, basic edits only, no effects etc are not imported.
Is there a third party effect in the VMS17 project file or an unsupported image/video/audio file - if so this may be what is causing the crash.
John EB
johnbaker. First of all, thanks for taking the time to review my issues.
I created 2 separate posts because the problems are happening for 2 different vf projects. One crashes and the other doesn't pan or zoom. I didn't expect that the 2 posts would be considered to be for the same project.
The one that won't pan or zoom has mp4, mp3, and jpg files.
The one that crashes has MOV and WAV files. I don't see any special effects.
Hi
Thanks for the clarification, that helps.
The project which won't pan or zoom is as I commented previously.
The issue with the MOV / WAV files may be due one or more issues:
What is your computer specification, Windows version and program version, see this topic for what is required and please quote processor and graphics card make/model in full, and also what monitor/screen resolution(s)you are working with if this is a laptop.
Are the graphics card drivers up to date?
A screen shot of the Program settings, Device options tab would help.
Download and install MediaInfo and analyse one of the MOV clips and post the results, see this tutorial on how to setup MediaInfo and analyse a video clip for all the data required.
John EB
Can you unlock the original post (Project created with MS17 Platinum crashes with MS 2023 Platinum) so that I can respond there?
Hi Tom.
These forums will only deal with Movie Studio 18 and onward as they are Magix Movie Edit Pro developed programs re-badged and not actual Vegas team developed programs (Vegas Movie Studio 17 and earlier) which are dealt with at the Vegas forums found here. Vegas Movie Studio 17 questions are dealt with there. I know that sounds absurd but they are differently developed programs with different sets of users. It gets more confusing as Magix Movie Edit Pro has now been renamed Movie Studio but has retained the Magix suffix of using the year (2023) rather than the upgrade release number. So the base programming of the programs are different. The encoding procedures are different and the problems with the programs not running as expected on a given operating system are different. In short we can't answer Vegas related questions on these forums. We try to help those who have decided to transition to Movie Studio 2023 from the Vegas program as it has it's own set of problems and solutions not relevant to Vegas product problems.
Ray.
CubeAce, You and johnebaker are giving me conflicting advice. He said to add troubleshooting information (see johnebaker wrote on 12/25/2022, 9:37 AM) and you are saying I'm in the wrong forum. The issue in question regards a MS17 project that crashes and won't display the crash log when opened in MS2023. I thought that this is the correct forum for MS2023 issues. The MS17 forum told me to come here with this issue.
@Tom-Lamson Yes, this is the correct forum for MS2023 issues, and the Vegas forum is the correct forum for VMS17 problems.
Problems opening VMS17 'vf' files in MS2023 is a MS2023 issue.
Hi.
I put the last information in because you asked for the other topic you opened regarding MS 17 to be reopened.
That is an irrelevant topic and any additional comments or information should be continued here.
Ray.
Hi Ray
. . . . I put the last information in because you asked for the other topic you opened regarding MS 17 to be reopened. . . . .
The problem @Tom-Lamson is having is, as @ericlnz has commented, is an issue with 2 different VMS 17 project (.vf) files being imported into MMS 2023, one opens, with only basic edits as expected, the other project is crashing MMS 2023 on import.
As this topic has evolved to cover both issues, it would be best to keep to this thread.
Are there any significant differences between the 2 projects eg effects used, different format source video files, 3rd party plugins etc?
John EB
OK, keeping the issue in this thread:
Copied from original thread: File/Open vf project that worked with MS17 Platinum. It crashes. Followed directions to restart. I hit button to display crash log and nothing happens.
Copied from this thread: The one that crashes has MOV and WAV files. I don't see any special effects.
What is your computer specification, Windows version and program version, see this topic for what is required and please quote processor and graphics card make/model in full, and also what monitor/screen resolution(s)you are working with if this is a laptop.
Windows 11 Pro version 22H Processor: Intel(R) Core(TM) i7-8700 CPU @ 3.20GHz 3.19 GHz
NVIDIA GeForce GTX 1060 6GB
MAGIX Movie Studio 2023 Platinum Version 22.0.3.167 (UDP3)
Are the graphics card drivers up to date?
yes
A screen shot of the Program settings, Device options tab would help.
Download and install MediaInfo and analyse one of the MOV clips and post the results, see this tutorial on how to setup MediaInfo and analyse a video clip for all the data required.
There are several MOV files all created at the same time in the same way. Here is one:
General
Complete name : I:\Videos\BarbaraAllen\L5\P1020148.MOV
Format : MPEG-4
Format profile : QuickTime
Codec ID : qt 2007.09.04 (qt /pana)
File size : 888 MiB
Duration : 4 min 0 s
Overall bit rate mode : Variable
Overall bit rate : 31.0 Mb/s
Encoded date : UTC 2015-03-22 12:16:11
Tagged date : UTC 2015-03-22 12:16:11
Writing library : pana
IsTruncated : Yes
Video
ID : 1
Format : JPEG
Codec ID : jpeg
Duration : 4 min 0 s
Bit rate mode : Variable
Bit rate : 30.7 Mb/s
Width : 1 280 pixels
Height : 720 pixels
Display aspect ratio : 16:9
Frame rate mode : Constant
Frame rate : 30.000 FPS
Color space : YUV
Chroma subsampling : 4:2:0
Bit depth : 8 bits
Compression mode : Lossy
Bits/(Pixel*Frame) : 1.111
Stream size : 879 MiB (99%)
Language : English
Encoded date : UTC 2015-03-22 12:16:11
Tagged date : UTC 2015-03-22 12:16:11
Audio
ID : 2
Format : PCM
Format settings : Big / Signed
Codec ID : twos
Duration : 4 min 0 s
Bit rate mode : Constant
Bit rate : 256 kb/s
Channel(s) : 1 channel
Sampling rate : 16.0 kHz
Bit depth : 16 bits
Stream size : 7.32 MiB (1%)
Language : English
Encoded date : UTC 2015-03-22 12:16:11
Tagged date : UTC 2015-03-22 12:16:11
Thanks for the help!
Hi
Thanks for the additional information that helps a great deal.
From the MediaInfo data the MOV file video format is JPEG encoded - this is an encoding format not supported by MMS 2023 natively and requires Quicktime to be installed.
If Quicktime is already installed I would suggest re-installing using Revo Uninstaller free to start the uninstall and clean up files and folders left behind before re-installing.
The file format should then import correctly.
To confirm the UHD 630 drivers version should be 31.0.101.3790 / 31.0.101.2114 and GTX 1060 drivers version 527.56 (31.0.15.2756)
HTH
John EB
I uninstalled Quicktime using Revo and scanned and removed leftover files. I opened the vf file and got the same error file.
Closed and reopened as before and "Display crash log" still did not open anything.
How do I check the UHD 630 drivers version?
Hi
As I previously commented 'using Revo Uninstaller free to start the uninstall and clean up files and folders left behind before re-installing'
. . . . How do I check the UHD 630 drivers version? . . . . .
To check the actual driver versions installed (for any hardware):
Press the Windows key and type Device and select Device Manager then follow through the video below - this is on Windows 11, Windows 10 is similar.
HTH
John EB
I'm not sure why you thought that I didn't re-install Quicktime AFTER uninstalling it. I uninstalled it and then re-installed it.
UHD drivers:
Hi
Look at your previous response:
. . . . I uninstalled Quicktime using Revo and scanned and removed leftover files. I opened the vf file and got the same error file. . . . .
The natural assumption is you did not re-install Quicktime.
Given that one project loads into MMS 2023 fine, as it should, and the other project crashes MMS 2023, it would be safe to assume there is something in the second project, or less likely that it is corrupt, that is crashing MMS 2023.
John EB
Thanks for your help. I'll just us MS17 for that project from now on.