[George Dean]

Hi Terence,

You have jogged my memory, and although I don’t recall the specifics I do now remember you had some previous threads fighting the m2t files and available disk space with your large and multiple projects.

It’s good that you reported the bug, as it may not just be in v16 beta but also in v15, just so obscure that others haven’t found it or haven’t reported it.

Anyway, best of luck getting things in your project linked up and finished up.

Best Regards……George

[George Dean]

Hi Rob,

Although Magix has improved Vegas Pro since they purchased it, they are still doing catchup with both stability and features attempting to get it capable with other mainstream NLE’s. I doubt they will ever top out Final Cut Pro Premiere or Resolve.

I switched from Vegs Pro to Resolve 15 Studio last year and other than helping others with VP from time to time (because I used it for so many years), I have never looked back for my production projects. Resolve 15, no doubt has the best color correction and grading capability of all the NLE’s and with v15 the editing and FX capability is really improved enough for me that I have no need for all the other programs I had to use with Vegas. Resolve 16 even jumps further with improved Fusion, audio and Fx’s, although v16 is still in beta and hopefully the production release will be in the next few months.

Depending on how complex your workflow and the feature set you need, will depend on which NLE will work best for you. I don’t have a need to work with any other companies, but if you have other clients who are using something like Premiere, it does present an issue when trading/passing on projects.

I have read many times from users who started with Vegas, progressed their editing talents to the point they developed paying clients, but are constantly beating against a wall with other production houses which have never accepted Vegas as a professional tool. If I were in it for the money (I’m retired now) I would switch in a heart beat, embrace the learning curve and get the monkey of poor acceptance off my back.

You may be right, it may be time for you to make the switch. Good Luck with your decision and future editing.

Best Regards……George

[George Dean]

As others have pointed out……

Phone support for Resolve is for the studio version ($300). You can get support from the community at the Resolve forums for the public (free) version. The Resolve Facebook page is for professional users of Resolve.

Regardless, you are not going to get a lot of support for a lot of issues for the beta version regardless of it being the free or paid for version. Resolve released the beta version for users of all levels to report bugs and problems so they can address those issues in future releases, not spend time with end users to fix it in the current release.

Beta versions are for testing, not production. By using the beta version you are a community free tester, one of the guinea pigs! One of the most important parts of being a tester is to include the log files when reporting bugs and issues. Development uses the logs to determine what is happening in the background, the part as a user you do not see, and help them discover the question ‘why’.

I don’t understand your comment about 16 beta being “more intuitive” than v15. It is the same interface, but whatever works for you, just keep in mind if you are doing production with a beta version you can expect errors, problems, issues, crashes, and instability.

Best Regards……George

[George Dean]

Hi Rob,

No, I’m saying that the ancient version of Vegas Pro 13 needs a 32 bit discontinued program to work with ProRes or DNx. Vegas Pro 15/16 will work with ProRes, but even it needs Quicktime for DNx. You could use Premiere or Resolve to natively work with ProRes and DNx.

Best Regards……George

[George Dean]

Hi Red-Rob,

I think that list is current, but you can go to index help in your version and search for smart rendering and you will see the same or similar list.

Best Regards……George

[George Dean]

Hi Rob,

You will need to load Apple Quicktime (best version would be 7.7.6). Keep in mind ProRes and DNxHD are 4:2:2 10 bit, and to retain the 10 bit for processing you will need to work in 32-bit floating point rather than 8 bit. You can not render out ProRes, but can read and render DNxHD after you have installed the Avid codec. DNxHD 10 bit codec should provide a rendered file in 10 bit (provided you are processing in 32-bit floating point).

Hope this helps….

Best Regards……George

[George Dean]

Did you try the free trial of MS16 Platinum?

Best Regards……George

[George Dean]

HI Gabriel,

Sometimes we do ask questions that make no difference. Other times the questions we ask are to assure us we are not running a rabbit down the hole. So, I agree, the file specs you posted should not cause any problems loading.

Let’s go back to your opening thread statement…..MS15 worked when you originally installed it, and now using the same source media it fails. If you have performed a full reset (as I posted above) and that does not fix it, after the full reset do a complete uninstall and clean install. If that does not fix it, it may be something in your system has changed and causing the issue. That may be a Windows update especially the graphic driver may have been updated and MS15 doesn’t like it. In that case you may want to roll the graphic drivers back to the previous version as a trial to see if that helps.

If none of that leads to an improvement, you may want to consider downloading the free trial version of Magix Vegas Movie Studio 16 Platinum and see how it responds to loading your source video. Both MS15 and MS16 Platinum can be installed at the same time, they are independent of each other.

Best Regards……George

[George Dean]

Hi Gabriel,

Thank You for the information. The info from Mediainfo is the MS15 program file. We need the file specs info from your source media, the video file that you are trying to add to your Movie Studio project. Please post those specs.

Also, in MS15, before you add anything Go > Options > Preferences > Video tab and in the ‘GPU acceleration of video processing’ select ‘Off’, then ‘Apply’ then ‘OK’. Then shut down MS15, start it back up and try to add your source media. That may help.

Best Regards……George

[George Dean]

Hi Gabriel,

Can you provide more information?

– What build number of MS15
– Your system specs, drivers, and OS, including graphics card.
– Using the free app Mediainfo (in text mode) post a screenshot of the report Mediainfo gives of your source media.
– Try a full reset, while holding down the ‘Ctrl+Shift’ keys, double left click on the MS15 desktop shortcut. A small window should appear, check the box ‘Delete all cached application data’, the left click on ‘Yes’. This will reset all MS15 settings back to factory installation, and delete the pesky cached application data which sometimes will cause MS to do strange things. (BTW: Uninstalling and Re-installing MS does not delete this cached data).
– If you can upload a small sample, maybe a few seconds, of source media, here, others may be able to determine better the issue.

Best Regards……George