George Dean
Forum Replies Created
-
Although I paid for the VP16 upgrade it finally convinced me to dedicate to DaVinci resolve. So my last several small projects have been completely in DV15, no crashes, no drama, just enjoyable cutting, FX’s, color corrections and rendering.
I still have an open support ticket with Magix, which is working on an issue with VP15/166, but not resolved as yet. I’m pretty much going to put VP16 on the back burner for now, maybe after a couple more updates, it will settle down and I will try it again, but by that time I think I will have learned enough keyboard shortcuts in DV15 that I will not have any desire to return to Vegas Pro.
Best Regards……George
-
Glad you got it working Michael. Sometimes just shutting down and starting back up will set things straights.
Best Regards……George
-
Hi Michael,
If I understand you correctly, two keyframes is all you should need. It works smooth for me. You might want to start clean with a new project and perhaps do a full reset of Vegas. There may be something in the cached application data that is causing Vegas to misbehave. Hold down the ‘Shift+Ctrl’ keys then double left click on the Vegas Pro desktop icon. Before clicking on ‘Yes’ check the box ‘Delete all cached application data’ . This will delete the un-needed cached application data that sometimes will build up and confuse Vegas and also reset Vegas to the original setup when installed.
BTW, although haven’t tried, Track Motion may be another tool for this job depending on the exact results you are seeking.
Best Regards……George
-
HI Courtney,
I don’t have a solution for you with the little information you have provided. Can you post some screen shots of your Project Properties, Render Template, Mediainfo (in text mode) screen shot of your source media specs, some details about your system, such as desktop or laptop, CPU type and RAM, GPU model and RAM, etc.? The more information about your system and your project, the more likely someone will be able to assist.
Best Regards……George
-
Ole, Thank You for your interest in solving my issue and your time. I got it. Had to adjust the sampling rate in my sound card.
Best Regards……George
-
Hi Ole,
Here it is…..
Best Regards……George
-
I’m glad that has worked out for you Paul so far. As Francois posted Handbrake can save you from problem in Vegas caused by veriable frame rate source media, if Vegas has a problem with it. Some VFR source media causes Vegas to do strange things and other VFR source seems to process well.
In my experience if Vegas handles viewing and editing the VFR source it will render without problems. With that said, I very seldom process VFR source media. If it does then using Handbrake to convert the source before putting into Vegas will help. If you have any problems rendering, I would suggest to Frame-Serve directly out of Vegas into Handbrake for the render. Here is an excellent How-To:
and here is a good Handbrake How-to:
Best Regards……George
-
Hi Paul,
Your source media is progressive, so change the Project Properties ‘Field order:’ from ‘Upper field first’, to ‘None (Progressive scan)’. Also in Project Properties at the bottom change ‘Resample mode:’ from ‘Smart resample’ to ‘Disble resample’. Then match your render settings to your project setting and see how that looks.
Best Regards……George
-
I have none.
Best Regards……George
-
I have successfully used both the Atomos Samurai Blade (HD) and Atomos Ninja Flame (4K) with a Canon XL2 and Panasonic GH4. The Samurai Blade is SDI and HDMI, the Ninja Flame is HDMI. They produce ProRes 422 HQ and DNxHD, and both work in Sony Vegas Pro 13 and Magix Vegas Pro 15. With ver 13 you will need Quicktime, with ver 15 you do not need Quicktime to process the ProRes. DNxHD in either version only needs the Avid codec installed.
Best Regards……George
