ok, thanks,
unfortunately i can only download build 394 of V12 from here, where i use 770.

770 is the last? It often freeze with TD30 and gopro files. Timeline and rendering too.

Any other software works great on my PC :(

770 is the last?

Yes

It often freeze with TD30 and gopro files. Timeline and rendering too.

There was a major fix for GoPro playback in VP13 build 453 that also fixed a similar issue with footage from DJI cameras etc.. If you have VP11 there is a workaround to use the codec from that in VP12.

thanks, i use that dll...

My problem is not choke, instead a real freeze. while simple timeline playback, and rendering at random portion of the timeline. I have i7, 16g ram, gpu turned off, etc..

I speak about this issue, which occured in every 15 min while editing :(

http://kepfeltoltes.hu/161101/fagy_www.kepfeltoltes.hu_.jpg

Source file isnt broken and the drive connection/condition is 100%
I'm going crazy, because every freeze need an app kill, and reload project which needs around a minute.

I even rolled back the original mc_dec_avc.dll but that doesnt help either.

Do you see that only in the playback or also in the rendered file?

And you see that with Vegas Pro 12 build 770?

Have you tried later Versions of Vegas Pro, maybe VP13?

Do you see that with GoPro Footage or with TD30 footage or with both?

On rendering file i never saw such frames. But rendering (via frameserver) often freeze too, maybe exactly when this happen at decoding process.. Yes, V12/770, i don't have V13.

I occured with TD30 footage for sur, i will check if gopro footage also produce this. Maybe just a 3D l-r decoding issue. But then, many people should have this bug..

Hmm, I have not seen that with TD10 footage here. But VP12 is an old version and my last s3D project was with VP13 (I have not tried s3D with VP14 by now). And for sure we will have different machines too.

I am not so sure how many users are still editing s3D. My impression is that this figure has gone down. In combination with an older Vegas version that could mean that we have not reports about that behaviour maybe, or do not remember such findings any more.

I do not know why the render process freezes if you use frameserving. Maybe it is due decoding, maybe not. There can be a lot of errors.

That is such a typical issue where support and help about a forum may not bring you a clear solution. Maybe the only recommendation could be to try to work around that error:

- either by using another encoder for rendering

- or by trying to do the same with later Vegas versions

Sorry that is not much.

OR i go back to Vegas 11 or 10 :) or even Vegas 8 in which i made my first 50min 3D film :)

those old nice days..