Jerry,

Thanks for that. I actually searched before I posted, but somehow didn't see that.

I suppose it is not a big deal for most people since I guess most don't render uncompressed. However, I got a PM from someone a few days ago asking if I could help fix my old Deshaker scripts which don't work because of all the updates to VirtualDub, Deshaker, and Vegas. So, I updated everything and got it working (I thought) until this person pointed out that rendering out from Vegas using uncompressed doesn't work. In tracking it down I found out that the template not only doesn't show up in the Render As dialog, it isn't even available via the script interface.

Oh well ...

> "I suppose it is not a big deal for most people since I guess most don't render uncompressed"

I agree that it's a huge deal because that's the way I tell people to make custom render templates since the "Default" was the only template that was guaranteed to contain your project properties. It was perfect for making new templates.

This is really going to be missed (at least by the three of us). lol ;-)

~jr

I shall add my voice here - this again appears to be something that was overlooked by SCS rewrites of the software - without realizing how and why so many users could benefit from this feature.

It is either a feature of software design forgotten, or misunderstood or possibly a whole lot of both.

SCS needs a mechanism by which they can learn from the user community and not arbitrarily drop beneficial features.

I would REALLY miss that template, as I render all my :30 spots to uncompressed for archive...about 1.16GB per spot.
Very useful for compositing as well.
What were they thinking? Doesn't seem like it would be too difficult for them to put it back in.
Ken

... the "Default" was the only template that was guaranteed to contain your project properties.Yes, that's exactly why I used it and why it was (past tense, unfortunately) so important.

I sent a bug report to them, although I'm not sure I was able to fully get across why its omission is so important.

Erm . . .?

Isn't the Uncompressed the one waaaaayyyy down below the VFW Menu, and within the Drop Down? If that's the case, then wouldn't it be a step to make an Uncomp'ed Template and make it a Fav? - If that's the case. True, if this is the case, then it's a PITA, but if it's the case that it's there, make one?

Or have I got it all wrong?

If I'm wrong, I'm wrong . . . . . .

G

Now I'm getting worried.
It seems we can not use Avid's DnxHD codec because of this yes / no?

Bob.

I jut did a 9 Track "Uncomped" ( I believe) Prerender of 1440x1020 50i, Track Motion test. I then Rendered this to MP4 for delivery to a Client's Drop Box. Looks Fabo. BTW, it all happened blisteringly fast too.

I'm trying to get to "value" here.

Cheers

G

"It seems we can not use Avid's DnxHD codec because of this yes / no?Bob, I've had no problems with my DNxHD renders on my Vegas 11 64bit (phew!).

I will mention (and clarify?) that all Default video templates are missing. In other words, it's not only the Uncompressed avi. The only Default templates that seemed to survive the upgrade are in a handful of audio encoders.

Sigh,
...Jerry

Can't we make one and make it Default?

G

"Can't we make one and make it Default?Well, you could, but the "beauty" of a Default Template is that it matches your Project Properties. If a user creates one, it may-or-may-not match the current project properties.

...Jerry

Hah! Well, now I know..

We want it back! NOW!

G

"Bob, I've had no problems with my DNxHD renders on my Vegas 11 64bit (phew!)."

Thanks for that and phew.

Bob.

It all started when I posted having changed the original JM script to work with Deshaker Version 3.0 and the latest version 1.9.11 of VirtualDub. See the last two posts in this thread. The reason using the JM script again is that New Deshaker is not compatible with the latest Deshaker and VirtualDub.

wwaag asked if I could make it available.

I used a series of Cineform templates to cater for the various event properties which works for me. I wanted to simplify that part by making use of the Default template but could not get it working. Also I wanted John Meyer to first check what I did before making it available. In an effort to try and solve my problems John kindly updated his original script but then found that the problem is with the Default template in Vegas 11 (which can still be invoked via scripting – but does not function as before).

John has sent me his update, which is basically the same as mine, apart from constructing the command line and choosing the render template.

I will have John look at my changes and then decide what to make available.

Edit: No problems using DNxHD.

Willem.

After exactly one month, I received a reply from tech support (copied below). They do not acknowledge the problem and instead merely thank me for my "product suggestion."

Since when does any company classify the "re-inclusion" of features which they remove (intentionally, or by accident) as a product suggestion?

Sigh ... it has become very discouraging to deal with SCS. The only good news is that, when asked a few months ago to become a beta tester, I declined, because I didn't want to spend dozens of hours testing something, only to have my "suggestions" treated like what you see below (and this is not the only example from the past few months).

I can at least now feel good that I didn't waste my time, but it hurts to see such a great product, and what was formerly such a fantastic team, now acting like this.

Here's the response I received today (but with the support person's name redacted).Hi John,


So, unfortunately, when I said in my original post above that the "default template" was gone, probably for all time, that appears to be the case. They sure have removed a lot of great features over the years: (RIP pan/crop path; ability to modify default script folder location; drop VEG files on the Vegas title bar to open them; and more). I've written to SCS when each of these features disappeared, but they never came back, and SCS didn't seem to care.

Our only hope might be for all of us to chip in and buy you a ticket and a tent :)

Bob.

This seems to be happening more and more these days. Another piece of software I use, a vector program, dropped things in the previous and latest version that had been around forever and used by me all the time. Support's response was a little more direct than Sony's. They simply said "We..." (meaning the developers) don't think our customers need this." Well, my response is "I, won't be using your product anymore!" And I started in 1996 with their software on a floppy disc. I guess I'll be sticking with VP 10e for a long, long time while VP 11 catches dust on the back of my edit desk because the easy of using John's deshaker script and the results were better than anything else I've found. Another vote for "uncompressed avi".

I definitely cast my vote for "uncompressed avi" and will go further in voting for a return to the interface and operability of "render as" in previous versions. My problems with 595 are all in the rendering department, editing has been acceptably stable for daily use, but things that are cropping up for me have forced me to return to VP10 simply for confidence in rendering. If implementation of GPU acceleration is responsible for the rendering weirdness I see. at least provide an option to bypass any new GPU code and have "render as" work as before.

Other threads have repeatedly mentioned disappearing/reappearing templates. I can't render anything in Sony AVC ("unknown error"). I can no longer render to Matrox i-frame MPEG2, which was my favorite way to generate intermediate clips with alpha. Can't render DNxHD with alpha. Some custom settings in MC AVC now generate errors where they rendered fine in VP10. And for me, all this is with CPU only rendering, all new templates based on VP11 presets, not imported form 10. Previous builds of 11 gave me intermittent rendering errors (although none allowed rendering to the Matrox codecs or DNxHD with alpha) but this build is consistent in that I have several rendering templates for broadcast delivery that simply will not work, although they did before.

Used SCS recommended clean install for build 595, removed all third party codecs and registry entries before installing 595, then installed only Avid and Matrox codecs. As I said, editing has been quite pleasant. Too bad I can't open my projects in 10 to render them.

I guess after purchasing V11 and not yet installing it...it will be a software I will never use or update. I render everything in uncompressed. Especially our animation. To me....this is a sad day for anyone using this software in a professional manor. I have been a user since Vegas 3...I guess it ends here unless there is a better way to render out my projects with alpha's and full resolution! It's a must for animation!

Mike

Just to be clear on two point:

1. You can still render to uncompressed. There simply is no template for that option, and because there is no template, you can no longer get the automatic adaptation to the project properties. This feature of automatically outputting to a resolution and PAR that matched the project properties is what made this feature so useful.

To render to uncompressed, choose the AVI type and then in the Render As dialog, find the custom settings, change all your settings (resolution, PAR, etc.) and then choose "uncompressed" for the template.

2. Don't bother asking -- and certainly don't ask in these forums -- for the return of the feature that has been in Vegas for the previous ten releases. None of the features that SCS has capriciously removed in past releases has ever been reinstated.

I get the impression that there is a slight misunderstanding as to what is missing.

Uncompressed is still available for render to avi. Any custom template may be created selecting uncompressed as the video format from the drop down list. No change as far as I know from that.

What is missing is the Default Uncompressed avi template. That was used to render to an uncompressed avi file automatically matching the properties of the original event. This is no longer possible - the project properties are now used and it can only be invoked using scripting. The net result of this is that a lot of scripts are broken (including John Meyer's very useful Deshaker script).

Edit: Beaten to the draw by the man himself - I must learn to type faster.

Willem.

Sinking ship...