Having done a few experiments some time ago with a Full HD 50p media flow from camera through Vegas through a Dune netplayer to a 50p capable 58" plasma - I remembered that Vegas could do this - so I just tried again:
But here it seems that I can only render to mpeg2 full HD 50p in Vegas 10e while the new Vegas 11 B 682 just says "An error occurred while creating the media file ... The reason for the error could not be determined" (the usual somewhat cryptic Vegas language for "bad codec settings")
PS: What I found out doing these experiments, btw., was that 50p does not improve the end-user experience - rather the opposite - seemingly because full HD AVCHD 50p at my available cameras (Sony HDR 690/700) is compressed to 24-25 Mbps while the substantially more bandwith-demanding 50p is compressed down to some 28 Mbps - only 10 percent more - and this is noticeable too much pixel-squeezing.
So I stay with full HD 50i at 24 Mbps from the camera and render the result to full HD 50i to at 32/28/22 (max/avg/min) Mbps - which seems to be the optimum for the types of videos that I make (documentary and travels).
If I know - when I record the video - that I'm gonna pan/crop or slow-mo the media, I do switch the camera to 50p for these recordings - as this seems to give me the best results (without the interlacing "noise").
Just 0.02 US from yet another happy video amateur in the sixties :- )
If you look at past VVPro release notes:
V8.1 was released in September (added 64bit for 1st time)
V9e was released in May
10e was released in June
Therefore I expect the final V11 update in July and that it will be the last one until V12 which will likley be introduced in the fall like the past few years. IMO only a handful of of the design team are still working on remaining V11 issues & the majority are working to get V12 ready for the release deadline. However I do expect them to fix the GPU rendering issues since GPU rendering improvements were a major advertising point to get folks to upgrade from V10 to V11.
Thanks to folks on this thread, who have basically served as V11 BETA testers for the last 8 months, we now have work-arounds for the notorious Render to Black & Replacement Footage bugs that have been with us since at least V10. June was the first month that I was able to use V11 for paid work. Although I will buy the V12 upgrade for $140 per license when it is first released, I will not install it until 2-3 revisions later - when folks on this forum report success...
I have found the same as ritsmer. My version 10pro rendered mpg2 1080 50p no probs, but the template suggested to customise was exactly how I did it and get the error message stated.
This is now not such an issue as I have found an AVC mp4 I can render out at 1080 50p, but while I was experimenting it was looking at one point I was well and truly stuffed....
I'll keep fingers crossed for the new build, I've never had GPU issues, just Mpg2 errors.
PS I had put on my system specs, but forgot to check the show box - now done.