I'm doing paid work in VP9e. There are some really nice features in VP10, but running 32bit here with 2gb must be a limiting factor.

Grazie

It's beyond me why people use 32 bits. Seriously, I used to of course because there used to be no other choice, back in the stone age. My 64 bit system is all around stable, and I'm running Vista! I think Vegas has crashed on me once in the last year. It's 99.999% dependable, and I think in my case it's because I have a decent computer, and I'm on 64 bits.

i would have to agree with the op - there's things broken in 10c that weren't even broken in 10a!

frankly i think the rush to 3d seems to have sidetracked scs from basic maintenance of what, until recently, has been a very good product.

i wouldn't go as far as to say i'd jump ship, but my future considerations will now take in other nle's more seriously (not that they haven't got problems).

it's a great pity that scs seems to have lost the plot in NOT supplying a reliable, robust nle BEFORE adding functions, and that in adding them they seem to be breaking more than they're fixing.....

"It's beyond me why people use 32 bits"

Because its advertised to work, it really is that simple.
No objections from me if they were as honest about it as Adobe are with CS5 and said it's 64 bits or nothing.

For what it's worth I do have a system running 10.0c under Wind7/64 and it seems to crash way less than 10.0c under XP/32 but it is still far from stable. It seems like it can only use 4GB of RAM which is a worry.

Bob.

"It's beyond me why people use 32 bits"

There are some of us who have big dollars invested in 3rd party products/extensions/plugins that don't work with 64 bit

"Is VP10c a piece of crap or what? Trying to render main concept Bluray 25mbit/s 1920 x 108 i out of AVCHD 1920 x 1080i (PAL). Just a plain vanilla project, with perfectly good AVCHD material on the timeline, straight out of a Sony SR-12E Handycam..."

Maybe it's a PAL thing because I'm not having any trouble at all doing exactly what you describe from a SR11 (NTSC)

Liquid, if you ain't got the courage to name me as one of "those people", then you are hiding behind anonimity for the sake of being helpful. It is mildly offensive and without value to me to make such a  statement. I come here to find and offer solutions to others. Your sweeping statement does nothing to assist my situation, and remains without thought or understanding.

As has been pointed out, it is advertised as to work with 32bit. If it is not supposed to, then I and others would either have to cut loose from Vegas or would have to ditch their financial investment in their present pc just to run VP10. 

Here's a thought, maybe you should inform Sony that "others" would be better off by spending their time in 64bit and not to purchase Vegas if they haven't got it. Maybe something along the lines of, first you need to upgrade to 64bit if you wish to use Vegas? Now that would be full of courage - wouldn't it? Do you know where the Product Suggestion page is? I could always tell you where to go.

Graham Bernard

hi liquid,

just to consolidate grazie's view. i heartily recommend vegas pro to my students (well, those who can afford it), all of whom i've come across in last few months (i'm pretty sure) run windoz 32bit (xp, vista, 7).

many of them are using pc's that aren't so new and that came with win 32bit, and they see absolutely no advantage to them to upgrade for the level of work they're doing (or can't afford to).

as pro's we might be 'forced' into 64 bit by the added advantages of say more ram, but to imply that 32 bit is old hat is a little pre-emptive.

however, i agree with you that 64bit is much better from a professional pov.

> "It's beyond me why people use 32 bits. "

Very modest of you to openly admit the limitations of your imagination or knowledge.

Thank you all for your comments. It's a good feeling to know I'm not alone with this problem, even if there is no immediate fix. The support of you all gives me the strength to" struggle" further :)

I have been running on 64 bits since the first MS operating system supporting it was published. I could have pointed that out in my post, albeit it's in my profile.

This error occurs in VP10c 32 bit on my 64 bit WIN7 ultimate system. I have 8Gigs of DDR3 ram. Trying out the 64 bit version of VP is not an option, as I have some essential plug-ins that are not (yet) 64 bit compatible. Exactly these same plugins works like a charm in VP9 (32 bit) on this very same PC - so it must be 10c that is the root of the problem.

I will probably spend the rest of the weekend trying to isolate the problem (I have no option). I start now in a better mood after a good nights sleep (with the help of some bourbon to erase my angst)... Yesterday evening was very frustrating...

I would just now pay a fortune for an application that converts VP10 projects into the VP9 format... The ultra-stable VP6 is just a faint memory...

I will also try the 64 bit version, and scrap my plugins and see if that helps. I will post my results...

Christian

EDIT:
---------------
Results so far:
- set preview ram down to zero mB - no effect
- rendering out only a smaller selection - no effect
- bypassing video FX on the problematic trax - no effect
- rendering same project from VP10c 64-bit (without the 32-bit codecs) - SUCCESS...

if it's any consolation christian, i installed 10 64bit only whilst keeping 9 32 bit for the plugins (new blue, spicemaster, etc.,). the truth is i haven't installed any commercial plugins in 64 bit and now haven't used 9 on any of my last 3 commercial projects.

i don't miss any of the plugins at all. i did dl genarts sapphire (and would buy it if not for a couple of the fx crashing 10 spectacularly - oh, i should say 10c, they worked happily in 10a - after a 5 minute load!). they're incredibly expensive, but there's literally nothing like them out there!

as it is, what i gain in 64 bit more than makes up for thecheesy fx in 9 32bit plugins.

It's probably not that hard taking your project back to V9.
1) You spent X hours on the project. Probably 80% if not more of that time was spent *thinking* about it. Remarkable how we can recall minute details like the exact frame we made a cut on.

2) See if you can render out any version of you errant project. Once you have a reference render drop it into V9 (or any other app or version) Given that you also did the original edit doing a matchback to a reference is tedious but not as time consuming as you may think.

2) Try running the script to Export as EDL and open that in V9. It may not be perfect but should get you most of the way there.

Bob.