Mark Barton
Forum Replies Created
-
Are you sure you asked it to render only the region you selected that is 90s? I would have expected long times with VP13 with 32bit color. Perhaps double check the Video Preview RAM setting on both 13 and 14 under Options/Preferences/Video. Sometimes this setting can impact render times.
-
There is also this plugin that looks to make it simple. I remember seeing this when the author was beta testing it and posting here on this forum.
https://www.fbmn-software.com/en/border.html
-
Did you check your Audio Device settings under VP14 options to compare with how it is setup in VP13. Not sure if you are using ASIO drivers, but perhaps VP14 did not carry over your audio settings. I tried the following and did not experience any problem with VP14.
#1 Dragged a video clip with audio (1080p mp4 created via Mercali v4 stabilization) – it was the first thing I found
#2 Added a song file from my itunes folder to a second audio track.
#3 Added three random sound effects wav files to a third audio track setting duration to 5s each and putting them back to back at the beginning of the timeline.#4 I saved the project and was able to play it three times in a row with no problems.
My Audio Device is configured for “Microsoft Sound Mapper”. -
I cannot get that link to work to see your example.
-
NewBlue support could tell you for certain, but I recall something along the lines that Titler Pro 1 was licensed for just the one version of VP12 and not all versions. I find Titler Pro 4 much more stable and useful and upgraded directly via NewBlue. That gave me the ability to use with any version of Vegas Pro, but also other editors too. It may be like my Boris BCC complete plugin, where I see the watermark with a new version of Vegas, but I just need to register it again.
-
I upgraded for $199 more for the hope that another version of Vegas Pro will come out. It is sad to think of all the hours of of development to address the legal issues with the name space for scripting and FXs that could have been used to enhance the product. I’m able to use VP14 although I have to change the way I do most things until the VASST FASST apps are updated. In the meantime, I’m using Vegasaur 3.0 much more than the previous version as it seems to be handling many of my uses for the FASST apps and Production Assistant 2, I had purchased first. I also like having the native ProRes support since Quicktime on Windows is not supported.
My main pain points currently with VP14 ate:
NewBlue Titler Pro 4 QuickEdit mode does not return to the timeline and I have to quit VP14. When I go back into VP14, my title is there as expected. I have no problem with Boris Red 5.5 as I just used that for motion tracking last night.
When I quit out of VP14, I notice in Task Manager that vegas140.exe is still running and sometimes multiple copies (Vegasaur Transcoder). If I see strange VP14 behavior, I exit and then terminate all those processes before relaunching again (or just reboot).
-
You need to go into the Shuttle Pro control panel and import the settings file found in the VP14 directory. It does the controls based on the executable running at the time. If you customized your a lot, then you may just want to edit/copy it so it is associated with the vegas140.exe
BTW, my ShuttleProv2 is working fine after I made this change, which I have to do anytime I upgraded Vegas in the past.
-
It installed fine on my Windows 7 Professional. Try running the installer as Administrator. I did not have to do that, but then the account I installed it with is already an administrator of the system.
-
[Thomas Roberts] “They had me at “hello””
+1 I probably will not need those features come this September, but I will purchase the upgrade if it is under $200 because of how well Magix has been communicating on this forum and hearing about the team they have assembled to revitalize the platform.
-
In years past it was usually the Nero drivers that caused problems. I had no use for Nero and removed it. You may have a use for Nero, so I only mention this if you needed something to try. Back then it was how Nero hooked in with a filter driver that did not always pass through control to other applications that needed to access the drive.