Comments

Eugenia wrote on 11/10/2007, 9:59 AM
This new version also adds support for Canon's AVCHD. Footage from the Canon HR10 works now on v8.0c.

But it doesn't fix the Cineform bug (you can't load Cineform files that were saved with Cineform's own tools, only with Cineform files created by Vegas version's of the codec). You can go around the problem by renaming the cfhd.dll file to cfhd.dll-OLD on the Vegas folder though (it will use the system wide cineform codec from then on).
MSmart wrote on 11/10/2007, 7:47 PM
I'm still using the "a" versions and have no problems. Nothing in the "notable" fixes apply to me. Should I upgrade?
4eyes wrote on 11/10/2007, 10:55 PM
Eugenia,
Are you speaking of VMS or Vegas? I had installed the cineformhd player which installs their codecs. I couldn't use my cineform files in VMS anymore and if I remember correctly I couldn't encode either. I removed the cineformhd player & all references in the registry, re-installed VMS 8 again and VMS worked with the cineformhd files for encoding & loading my old files.

It gets a little confusing between the VMS cineform dll & the Vegas cineformhd dll file. But if there was a problem I would think that this would be corrected in the updates, both VMS & Vegas.
Eugenia wrote on 11/10/2007, 11:40 PM
I am talking about VMS and Cineform NeoHD/V. VMS 8 has a bug (no, it's not a limitation) where it can't read files produced by Cineform's Neo tools. But it can read older and newer Cineform files created *by* VMS.

But for users with a Canon HV20 who need the Cineform tools to remove pulldown to their 24p files, VMS doesn't cut it anymore because it can't read these files (it's not a matter of 24p btw). The only way to go around the problem is to remove the cfhd.dll from VMS' folder and force VMS to use the system-wide version of the codec, installed by Cineform's tools.

Vegas Pro does not have this bug. It can read Cineform-created files from any source/tool/app.
4eyes wrote on 11/11/2007, 5:47 PM
Thankyou,
That will save me lots of time troubleshooting if I ever use Neo and run across the problem.
Himanshu wrote on 11/18/2007, 8:27 PM
Crash-on-exit that several people reported with 8.0b has been resolved.
RWatts wrote on 11/19/2007, 6:07 AM
I just upgraded from v6, and the ability to move tracks alone is worth it! I haven't explored other features yet, but in editing one long movie it was crisp in performance.
Ivan Lietaert wrote on 11/19/2007, 10:09 AM
I also upgraded from VMS6 to VMS8c Platinum. The process - from ordering to installing and registring - took less than 35 minutes.
What I like a lot about the upgrade:1) the newbleufx and transitions (very powerful) 2) the addtional audio plugins 3) the hd support