I'm keen for Sony to keep updating Vegas without too many thoughts on whether their users will be reluctant to use that next release within a reasonable period of time.

As I recall Vegas6 didn't need anything more than netfmwk1.1. When it was released it wouldn't even work with the betas of netfmwk2, probably by M$ design more than Sony's reluctance to embrace it. I'd give that laptop another try DJPadre.

Vegas6 and Vegas7 both like netframework2, directx9, win2k SP4 / xp any SP - for DV work.

I wouldn't change even a point release if you already have 7<something> installed and are mid-project. I never install new version first on my main edit PC anyway. To tell you where I am at - I'm using 7b right now but will have 7c on before the New Year. That is just because I've not been editing with Vegas for quite some time now.

Ushere,
I've been using 7c with no problems related to the software so far. However, I'm not editing HD at the moment. Thought I had a problem with it crashing during a render test but it turns out that was related to my system rather than the software. Needed to clean house before running the test. My son is also running 7c with no problems. Both of our machines are dual cores (one AMD and one Intel). Since you are between projects and not using Cineform, good time to install I'd say.
Randy

Not having any problems with DV or HDV or Cineform. Make sure you update the .net 2.0 from Microsoft automatic update site. You will then have 1.1 and 2.0 on your machine as they are two separate entities.
JJK

I think some of the issues that people are reporting have to do with their system integrity rather than the program itself. In this day and age, one cannot continue using a computer without some in depth knowledge of troubleshooting skills. I am not having any problem with Vegas 7.0c whatsoever.

it wont even install on my laptop.. keeps telling me i dont have netframework2 installed when i KNOW i do as im already running V6 without a problem..

Vegas 6 required .NET 1.1 SP 1. Vegas 7 requires .NET 2. It is quite possible that you do not have .NET 2 installed.

"and am like to use hd as mt2 on timeline (mostly cut to cut)."

That works fine for me...

To install .net 2 is not a big deal.

It's not a matter of system integrity. I have 7c crashing daily on a system that has nothing else on it, updated windows and two integrity programs checking daily. I think it must be about system design - the type of RAM, buss speeds or something like that. I know some say 7c works fine (but remember the problems are only with HD and Cineform and m2t rendering - nothing else. I heard one guy say 7c worked fine with basic DV? - not at issue) but some of the most experienced Vegas users there are all with modern machines and expert knowledge are having as many problems with 7c and m2t operations as anyone.

Michael

MH makes a good point. I'm working with Vegas 7c and Cineform files right now without problems, took me a while to get there though. Had to completely remove every trace of Connect HD (Cineform) from my system.

The key word being "some", as in "...some of the most experienced..." In this case, "some" is probably fewer than a half-dozen out of hundreds of Vegas users on this forum.

Most of us are having no issues with 7c at all. Vegas is still the most reliable software on my editing computer, bar none.

Steve M.

ushere, I have a few issues with vegas7c, but the overhaul performance is a lot better with 7c. I try to keep separate vegs for projects that have been started v6d or v7b just in case v7c does not do things right. V7c is going in the right direction. I just wish v7c had a command to build vegs for V7b to v6.

many thanks one and all, especially for taking the time out to reply during the festive season.

i have to say i'm tempted by the old saying, 'if it ain't broken, don't fix it'. 7b is working fine for me at the moment, and though i'm reasonably computer literate, i don't see why i should have to jump through hoops just to install a program (rather like m$'s usual help desk response of - first, reinstall windows).

i'm fully aware that i'm using one of the best (read; reliable, stable) nle's around - and that's after having experienced avid, fcp, velocity, etc., but this little hiccup, be it cineform, net 2, mismatched components, whatever, really has made me wary. from v3 onwards it was simply a matter of downloading and installing - no sweat, no bother... i've got to the stage where i simply want to sit down and edit, not figure out quirks in whatever.

i think i'm going to hang out for 7d - unless anyone can tell me that i'm really missing out on some fundamental change that will make a major difference to my general workflow (ie. mostly dv, with a view to mt2 timeline editing).

i would like to wish all the members of the forum a great new year, and thanks for the tireless support that's so generously given,

leslie

Another thing to consider "ushere". If you get into the details with them that say 7c is fine, you will find quite a lot of users who are saying V7c is fine aren't fully using it. If you are still with DV and do little Fx, color, generated media etc then I think you will be fine. I'm running multiple tracks of HD all with Fx and color correction and all using the Cineform intermediary and rendering to a HD format like m2t at full resolution. That's when 7c shows signs of not being able to cope.

Cineform came out with an HD Connect version 3.3 on the same day Vegas 7c released. Did this combo trigger the problems? Does 7c work ok with some other version of HD Connect? Anybody know?

I have had non-stop problems with capturing using Connect HD (Cineform 3.3.0) and trying to edit with V7c ......
I've reinstalled both softwares trying to clear out whatever is making the problems happen.

When I finally got my captures to work (HDLink kept stopping for no reason while capturing, and I had to keep restarting...the last time it wouldn't capture at all so I stopped headbanging and reinstalled) it almost seemed like the clips were corrupted somehow.
When I put the CFDIs on the V7c timeline I''ve had completely erratic behavior, freeze ups, the whole program just disappearing while playing, all kinds of weirdness.
This has never happened before with my previous Vegas programs...

Last night every time I put a third CFDI clip on the V7c timeline the whole program disappeared! Didn't matter which clip I used, the minute I tried to place a third clip on the T/L the program disappeared completely without any signs/errors, etc.

So I tried to put the third and fourth clips down onto a second video track and then I could work with it for a while although I couldn't get transistions to work and when I did a test render at the end of the render the whole program shut down unexpectedly and when I reopened I had an autosave situation.

When I tried to use the CFDIs in Cinescore the program crashed before I could even get the clips on the timeline making a loud weird audio buzz before seizing up.

I also tested HDLInk by capturing only m2ts (no intermediate conversions) and they captured fine and worked in V7c .

I tried SD clips in V7c and they did fine. So for me the problems seem to be with using the latest CF to capture and V7c not being happy with those types of clips....

And just to do one more test I took the same CFDIs and loaded into my V6d and they crashed there too, whereas in the past V6d has never been unstable or had any problems.

Have put in error reports with Cineform and posted crashes here and over on Cinescore.

Hope this gets fixed ASAP !
Frustrated.....

Teaktart

Vegas 7.0c for many people is having issues with still images and alpha channels. It can sometimes show artiffacts. I even had a few regular stills (jpg, with no alpha) and also had some issues with it showing cleanly.

Yes, I have been able to work around it, but I shouldn't have to.

Besides that, doing well here.

teaktart, sounds to me like Cineform 3.3 has serious problems, since evidently it won't capture for you. Possibly Sony tested with whatever version of the base VFW codec they are including with 7c, and not the full HD Connect. Well, if Vegas and CFDIs work fine for whoever doesn't have HD Connect, then Sony has probably done their part. If installing HD Connect 3.3 causes the problem, maybe it's because they rushed out that 3.3 build to match Sony's 7c release date? And they didn't do enough regression testing against different machine configurations? Whatever, it seems like Cineform needs to get a fix out for us.

I sure hope that happens. It'll require lots of user input (as you have done) to them so they can look at configurations other than what's in their QA lab and successfully reproduce the issues.

Jayster...
I've been trying to hone in on my sequence of problems but about a week ago I got a new CanonHV10 and shot some footage...
Came back and before capturing with ConnectHD I updated to the latest version and also saw that V7 now had a "c" version so did that one too.

At first the capturing seemed to work normally except that it didn't split the scenes right despite that being checked off and seemed to take an eternity to convert.
I noticed that my task mgr was reading high 90+% processing and my cursor would barely move and was very clunky if I tried to do anything else, which is not typical.

Each day I shot more and each time I tried to capture the CF got more and more erratic with unexpected stops in the middle of a capture, restart, stop,restart, not fun. I finally got my stuff captured but not fun, although looked good playing back.

Vegas started to crash and odd things started to happen. I kept having to reset my video preview to "preview", it would just change over to "good" on its own. It was also hogging processor according to task mgr..high 90s% for just simple clips/footage.

I didn't stand a chance if I tried to load the same CFDi clips into Cinescore stand alone. I think I did get somewhere when I used CS inside of Vegas but its hard to remember as it was crashing so often.

So I started with three variables: new camera, updated ConnectHD, and updated V7c and have been trying to get a grip on when/where the problems arose and progressed as every day its gotten worse. Reinstalling seemed to help the capture go right but the next day it snagged again with weird stop/start again happening.

I put older CFDI clips on V7c and some they seem to work ok, but were captured with earlier CF version and V6d.

At this point I'm stopping to de-frag C: drive and the main drive I've been using for all the testing and is a brand new interior drive so I'll clean that up before any more efforts.

I'm most curious if others are having similar behaviors. Tried to explain whats happened here but I think my brains are half scrambled with trying to find workable workarounds if I can for now.

Thanks for your input,
Teaktart

Staying with 6d until I see 7 is ready (fully). It's all i need anyway.
I suspect a version to correct memory handling will be addressed after the holiday simmers down.

Teakart -
I also have had some weird problems with Cineform 3.3 (w. Vegas 7c) -
now I have no experience with prior "bought" Cineform to compare to. (2.xx)

My problems were also instant crashes and corrupted AVI files - I just gave up capturing with ConnectHD and went back to m2t as captured by Vegas. No problems since, except preview with m2t on Vegas timeline is inconsistant in speed.

I'm watching the other thread on "Preview" to see what's listed there, in terms of upgraded hardware. I'm using a Duo Core (not Core 2) pentium 3.3, with SATA single striped drives.

I'm also NOT at any heavy editing situation right now, simply cuts, dissolves and a couple of minor color corrections and a slo mo or two. (Actually that pretty much details 90% of what I've been doing lately, anyway.

Bottom line - stock Vegas is doing the job. Cineform 3.3 is on the shelf until I hear more.

v

Sooo many factors involved with 7c, external to the program. XP has been patched so much a lot of it's original spunk is long gone. Also, people who are having problems: have you patched XP lately? It's been months since I have, and no 7c problems here. I use Vegas capture, build Cineform from Vegas timeline. Also on a second machine, XP barely runs now on my old dual 1Ghz P3, whereas I have done some HDV editing with it since V5.

Vic, I've noticed my inconsistent speed with m2t playback is related to the amount of movement in the footage, the more movement, the slower playback.

Also, I did install latest Quicktime (not Pro) on top of V7c, but who knows how that has impacted my system performance.

So we have, for example, 200 forum users, with 200 different installations of Vegas. Third party tools, some upgrading to the new Cineform codec, some not, different levels of XP patches, Media player 9, 10 or 11 Beta.

I think the only way to answer "is 7c ok?" is to install it on your machine and try it.

I love it. HDV timeline editing is much, much better than in the past.

I hope this is soon resolved. I for one have regrettably "gone backwards" to Vegas 6 for all my crashes, slow and stopped renderings to go away. Also I have notices with 7c when applying real-time audio Fx there is not enough memory available and the preview freezes while this works flawlessly in 6. Somehow 7 is hogging too much memory. For the record I have installed ALL XP patches. I have my machine update automatically. Anyone running 7c with Vista have anything to add?

Sure "misery lovers company" BUT....I'm getting a little tired of all troubles and little play here!

Last night I had a nice long session that started with V7c crashing when just adding some new CFDI clips to timeline. I tried to load a bunch at once....and crashed. If I added each clip seperately and cautiously "saved" after each clip I finally got my 20 or so clips on the timeline.

I was able to score the music bed using Cinescore as a plug-in on V7c timeline and get my preview to work. Yippee! I was neurotically saving after each move just in case it decided to crash again... Jeez I'm a little gun shy here... and got my project done in the wee hours of the morning. So that's wonderful.

BUT, Just now I opened Cinescore 1b as a stand alone program and threw up a couple of the very clips I worked with last night. Went to "generate music" and all of a sudden my video preview turns solid screaming red in color! Can't get my footage to show, Click OK and my music score shows up on the track and the program freezes up!
No autosave this time so I lost what I just had....this is not fun....

So, Is it Cinescore being weird when not used within Vegas?

Are my CFDI clips corrupt, even though I could use them last night (although I did hear some weird audio glitches/blips while playing from the timeline) ?

I have 4 GB of memory, but could there be a snag on how this is used?

I have even had my Windows Defrag freeze up time and again while trying to defrag a new hard drive, is it the software, the data, or the drive?

My whole system seemed fine till about two weeks ago when I "added" all the updates of software. (Also auto update Windows)

This is progress??? Ouch!

Teaktart

p.s. I just tested some m2t clips on Cinescore timeline, generated music, rendered, came out fine.
Took some of the above clips that had been rendered to CFDI intermediates (With V7) and put those on the CS timeline and again the screaming red screen of death and freeze up/crash....Lost project.
Took older SD clips on CS timeline, generated music, rendered, came out fine.

Tentative conclusion:
I think there is a problem with the converted CFDIs (vers3.3.0) no matter if converted by HDLInk at capture or later converted from m2ts within V7c (consistantly crashes with Cinescore every time and V7c too often)
And possibly other stuff is now affecting my whole system....