Comments

Tech Diver wrote on 6/13/2014, 7:29 AM
I'm not sure if this is related to your problem, but when I installed VP13 last week I forgot to set VP's internal memory usage from 1024 to 2048. As such, HitFilm was causing me all sorts of problems. After I fixed it, all behaved well. Note that I am referring to the setting called "Memory needed by Vegas 64-bit" on the Internal tab of the options menu.

Peter
ushere wrote on 6/15/2014, 1:55 AM
just tried it on gen media and a m2t file and both worked fine. what's your format?
OldSmoke wrote on 6/15/2014, 10:21 AM
I have been for ages on driver 296.10 and only recently moved up to 334.89 and I will stay on it for ages again. Don't change driver unless an app specifically calls for it and certainly don't let Windows do an automatic update on anything.

Proud owner of Sony Vegas Pro 7, 8, 9, 10, 11, 12 & 13 and now Magix VP15&16.

System Spec.:
Motherboard: ASUS X299 Prime-A

Ram: G.Skill 4x8GB DDR4 2666 XMP

CPU: i7-9800x @ 4.6GHz (custom water cooling system)
GPU: 1x AMD Vega Pro Frontier Edition (water cooled)
Hard drives: System Samsung 970Pro NVME, AV-Projects 1TB (4x Intel P7600 512GB VROC), 4x 2.5" Hotswap bays, 1x 3.5" Hotswap Bay, 1x LG BluRay Burner

PSU: Corsair 1200W
Monitor: 2x Dell Ultrasharp U2713HM (2560x1440)

NormanPCN wrote on 6/15/2014, 1:29 PM
I was heretofore under the impression that if a driver is new then it brings with it added features.

New drivers can fix existing bugs, and can have new bugs of their own. They can expose existing bugs in supposedly currently working/correct code.

For example, in NewBlue Titler Pro 2 a new AMD driver "caused" a problem with the display of the first letter of text. It was dimmed. It worked fine with the previous driver. I reported this to NewBlue and to AMD. In a subsequent NewBlue release the problem was gone, fixed, and I had not changed the driver or Vegas version.

If you are having no problems with a driver, then it is usually best to stay with it. If you have occasional GPU crashes it is worth trying new drivers and new Vegas versions.
dlion wrote on 6/16/2014, 7:40 AM
i had to roll back from 337... to 335 as titler pro 3 didn't like 337. in this case (only?) latest isn't always best.