re- net framework2
i have it installed for some other applications which have nothign to do with Vegas, but i reinstlled it and V7 installed fine on teh lappy.. ran as i expected, slightly faster in rendering... about 10% faster in fact... one thing which is interesting, is that i created a 1min slideshow set within a 720p 25fps timeline, now i rendered THAT out to MPG2 Sd... took about 2.10.. then i changed the project to SD WS 576p 25fps.. and it took 2.27
hmm..... scaling down took longer. maybe this has soemthign to do with the image resolution. who knows...

it'd be nice to see a sony tech get involved in this thread.
You 7c guys letting sony know these things? Sorry, I can't be a guinea pig this go round - too busy.

It's happened many times before. My gut's telling me 7 is in need of streamlining and needs to be gone over, it's just not utilizing memory correctly. 6d stays.

Had another crash, rebooted and got the blue screen of death!
Memory cache dumped...

"A thread tried to release a resource it did not own....
Disable any new software or hardware...
Disable BIOS memory options such as caching or shadowing, etc"

I don't have a clue what to do with that message except cross my fingers and,

Restarted and got back to normal desktop, whew! Editing??? How with all this crap happening? And its not just this machine my older computer with same stuff crashed too which it never did before with the same clips/software, etc.

Please Sony....we need a lifeline here!!!

Teaktart

good luck askin for a lifeline.. it aint gonna happen..

.. after v4, ud think theyd make some major improvements, the only real improvement ive seen is compositing and cpu utilisation, i see nothing new in the media generator or titler, i see no new filters or filter chain streamlining.. hell, vegas could be alot more than what it is, and for what were paying for thee ""üpgrades" one woul dlike to think that our cash is going to more r&d than what weve seen so far..
fair enough XDCam and media manager are now included, but cmon.. this is beyond a joke..

when beta 4 was released, the actual launch was nigh on perfect.. now though that testing is only to a very small group, we see these problems... and we as users are expected to put up with it and troubleshoot problems which shouldnt exist or shoud have been pinpointd at the ime of testing.. its not just about performance, its about Value for money, and ive seen every NLE on the market evolve in ALL ways.. and all vegas has done is evolve with the technology it lives on... thing is, every NLE has done this as well.. some more effectively than V7... so V7 offers nothing all that new..
These days vegas does the work, but thats about it.. performance wise, V7 on quad core or not, there are cheaper or cost equivalent solutions which offer far more realtime features, far more filtering and colouring options, far more efficient workflows without the need for intermediates... I could go into detail, but thats not whta this thread is about..

in the end, Vegas workflow is what has made it what it is, its a shame that the basics of most other NLE growth has been overlooked since V4...

"Please Sony....we need a lifeline here!!!"

I seriously do not think it is Vegas 7c. At all. I am not having any problems like described. It seems like most of the people with problems mention Connect HD.

I create my CFDI's from the Vegas timeline, I do not have Connect HD. I don't use any other capture tool except Vegas for both DV and HDV from an FX1. I have 2GB of RAM, P4 3.2. I haven't updated Windows since about the first of September.

I have spent a lot of time recently trying to get V7c and Cinescore 1b to break and I can't. I put 320 (three hundred and twenty) CF intermediates on my timeline, a few at a time, one at a time, many at a time, copy/paste a bunch at a time. No errors.

I just loaded a bunch of CFDIs into Cinescore standalone the same way. Can't get that to break either.

Those that use external capture programs, report the errors to the external capture program vendors. Those that use pure Sony tools and are having problems, report it to Sony, including mentioning any recent Windows updates. Microsoft has a history of breaking third party applications with Windows updates. If it is purely isolated to Windows updates and Vegas, report it and give Sony a chance to fix it.

I'm finding that with 7c my workflow is greatly simplified. Little need for an intermediate now unless it is in the lower nested veg level with heavy effects, or with complex color correction.

Happily editing away with Vegas 7c (and Cineform Codec version 2.5 when needed) ...

Dave

Hi fldave,
I'm jealous !

I spent the $200 on ConnectHD to save time capturing and with V6 editing/previewing. Until this stuff started its been well worth it.

In one of my recent tests I used Vegas captured m2ts that I rendered to Vegas intermediates and when I put those up on the timeline even those crashed for me....man, that hurt! So it sounds like I was trying out your workflow only I wasn't so lucky.

I've got my system on "auto update" with Windows which seems to be the prevailing advice, "don't get caught with your updates down"...

I have 4GB memory installed yet that seems a potential problem here especially with the 'dump' last night. Something ain't right...

Wish I was a natural born genius with this stuff....but alas, I was born way to soon to grow up just absorbing all this technology, I
have to learn it the old and slow way.... 'one bit at a time' !

Teaktart

Teaktart has the point. Sod being a video editor, you need be a computer nerd to run Vegas these days.

I'm stuck with programs that just won't work anymore.

I uninstalleded Cinescore and then checked V7c with some CFDI clips and it crashed, no way to get it to work at all, red screen frozen solid

I'll uninstall V7c next.

Any suggestions on anything else I should look for to delete that is associated with these two programs? That might still be left behind and could continue to screw things up? Where would they be located?

Any pointers on how to reinstall each program that might help troubleshoot?

Getting desperate to edit here,
Thanks for your help....
Teaktart

teaktart:
Maybe I'm daft and missed out on some of what you posted. But, have you tried completely dumping Connect HD for now? Totally uninstall Connect HD (and select "yes" when it asks if you want to remove the final codec part). Then uninstall Vegas and Cinescore. Then reinstall Vegas and Cinescore.

If you haven't done those steps, you may want to give it a shot. Seems like that would give you the configuration that fldave is successfully using (plus the Windows Updates).

Also, note this quote from the Cineform CTO on a different forum regarding Connect HD 3.3 and Vegas 7c:

"The issue you mention have not be confirmed as most users are running fine -- it more likely an installation problem as users who have done clean re-installs don't have any issues. New users are not haven't issues either. We have very few reports, so it more of a forum chatter than anything people are report to support. So at the moment there is nothing to fix. If there are issues, people are not reporting them by file tickets at cineform.com/support.

I have done extensive testing on this issue (that has been reported elsewhere in this forum) and I can tell you the problem is NOT in Cineform. A clean machine that has never smelt Cineform has, in my testing, many of the render crash problems described here.

Secondly, a clean 7c install is not a solution. 7c installed clean with a new windows system following a HD format showed the same problems that it had demonstrated on the machine before the format and clean reload. It seems to me that 7c just does not like some machine configurations, but I have failed to identify any specifics. The programmers who made the code changes from 7b to 7c DO KNOW (they must) but Sony, as has been pointed out here before, is mum on this issue.

Back again,

I have uninstalled all of the above: Vegas 7c, Cineform3.3.0, and Cinscore 1b (including the CS codec which meant none of my captured clips were visible in V7 or WMP)

I reinstalled one at a time V7c from website - rebooted
CineformHD from website - rebooted

Played CFDI clips on V7c timeline this morning and they seemed to work

Installed Cinescore - reboot
Open and add some CFDI clips
Generate Music - Lose Preview Window, goes black - Music shows up on audio track, click "Play" and it freezes solid...No way, Jose! each and every time

Open V7c add CFDIs, plays fine so far....
"Generate Music" Vegas works a couple of times at first
Try same thing later today and Vegas crashes, error, etc.

And just now I was adding CFDIs to V7 timeline and about 20 trimmed clips into it the program crashes, no reason

I absolutely cannot get the Cinescore to work either way: inside Vegas or as a stand alone.

And of course, I was just starting to get a handle on how to work the damned program along with my recent $200 purchase of themes!

What now? At this moment the CFDIs seem to work sometimes, and Cinescore not at all despite reinstalls.

Frustrated and stuck here,
Teaktart

I just completed a project (28 minutes) with CFDV clip (19 minutes) on V7c timeline with about 6 or 7 takes of Cinescore music the full length of the clip (19 minutes) with the Cinescore clips outputs routed to a spare SCSI 160 gig drive. If you don't route the Cinescore stuff to another drive it defaults to your "C" drive and quickly crashes your machine because it fills up the drive with about 6 gigs faster than you can say Jack Robinson. I had about 7 gigs left on my C drive and filled that up in about 30 minutes. Cinescore standalone has a problem with CFDV files in my machine but not in V7c.
JJK

I hate that Cinescore keeps wanting to shove files into C:
If I set another drive as default I want it to go there each and every time UNTIL I change locations

My question to JJKizak is: are you using V7c and setting up your properties so that all audio goes to a different drive than your video clips? i.e. Audio to D: and Video to E: ?

I keep all my materials/media for a project in one folder so I can find everything in one location. And when I render out sections or the whole project have that go to a different drive from where my project folder is located. Anywhere BUT C: drive !

Sounds like a lot of us just can't get Cinescore to work as a stand alone, what's up with that? I bought it as a stand alone early on, and I'm glad its incorporated into V7c, a major advantage. But it ought to work either way....

Eileen

teaktart:
Cinescore standalone works on everything I have except Cineform captured files. However, the Cineform files work fine when loaded to the V7C timeline. Don't know why.
When you select create music, select theme, then the (OK) second to the last create menu comes up then you select options in upper right corner before you start actually creating the music and it has "where to output cinescore files too" and select the drive you want. Then when Cinescore creates you will see that hard drive operating. You have to use the options after the second menu pops up in Cinescore. So in my setup:
Audio to drive "G", "D", "I", "J".
Cinescore Audio to drive "L"
Render to drive "I", "J", "H".
Application files on drive "C"
Veg files to drive "H"
DAR files to drive "F"
DVD-a temp files to dirve "G"
DVD-a TS files to drive "H"
V7c temp files to drive "G"
Saved TS files to external drive "N"
Forge temp files to drive "G"
CDA temp files to drive "G"
Theres more but there is some problem going on when you try to insert Cineform files into Cinescore.
JJK