[Si Tran]

I feel Brad’s frustration as I’m still using XP Pro – despite my Dell M-6400 mobile workstation is ready for 64 bit OS. The main reason that I’m not ready for the conversion is largely due to all my 3D softwares (Autodesk Maya and 3ds Max) are 32 bit and I got them installed “gratis” as part of work pipeline from my previous employer. The upgrade to Windows 7 would render those softwares useless but the good news is that Windows 7 is available in both 32/64 bit also in XP mode(which would work in Brad’s case or anyone that still uses 32 bit hardware and in favor of XP Pro workflow). But in my case, migration of my current 3D softwares’ licenses to new OS are impossible since I don’t have the original install discs(and I can’t afford Maya or Max license which runs about 6K+ each). The painful part that I can relate with Brad is that 10 days ago, upon launching Vegas Pro 8 (I have version 9 but it never worked well), there was the pop-up about Vegas Pro 11 update promotional sale(also, no details about OS compatibility), the deal was too good to think twice therefore I bought it with FREE training discs. Now, I will have to wait until I’m ready with Windows7 upgrade along with all my 3D softwares to start using Vegas Pro 11!

[Si Tran]

This has nothing to do with the aforementioned topic but it has a bit to do with the m2t bug that Michael N. mentioned here – First off, after upgraded to Vegas Pro 9, I discovered that it did not open project as fast as version 8, rendering also seems slower therefore I stick with version 8. Now, on to the problem with m2t bug – recently, I tried to open an older project which consists of multiple clips of m2t video, only audio came through but the video track was all black. Suspecting that version 8 as the culprit, I re-opened said project with version 9, same problem! I tried the same approach that helped fix my Vegas problem with Quicktime movies that I had in 2009: quit Vegas, uninstall QT, remove QT reg key, reboot PC, install QT version 7.6 (any later version would resurrect the Vegas m2t bug) – I could be wrong, but so far, Vegas Pro 8 is what I currently use and have no desire to touch Pro 9 albeit it’s considered an upgrade!

[Si Tran]

I also forgot to mention that both versions are 32bit and run on Windows XP Pro Version5.1.2600 Service Pack 3 Build 2600.
Besides the possibility of Codec’s flaw, the OS may have something to do with this too!

[Si Tran]

I just upgraded to Vegas Pro 9.0c (build 896)-
My project setting is HDV 720-30p (1280×720, 29.970 fps), when I tried to render a comp of AVI clips into MPEG-4 (.mp4) movie, the render was super slow, the movie was playable but anytime I tried to scrub, the QuickTime player just froze.
But when render the same project on Vegas Pro 8.0c (build 260), the movie came out fine, playable and scrub-able.
Then I did another test of said project with the Pro 9 to render a small clip (29MB)and a full length comp (382MB) with Pro 8, the large size movie still played fine while the tiny clip remained broken. I have the impression that something is seriously flawed with the Vegas Pro 9 codec. Not very cool with the upgrade – I’m afraid that I have to uninstall the new version and continue using the old faithful Pro 8!