As far as I know, there is no "real" info on Vegas 9, it's all speculation. I have no idea whether Vegas 9 will actually be released at NAB. A new Vegas version would provide SCS with a large infusion of cash as a result of all of us upgrading. I'm ready, I'm always looking forward to a new version of my favorite NLE.

Here's my short wishlist:

1/ Move from VFW to DirectShow. That would enable things like 10 bit video, a bit tighter compression without video quality loss, faster video previews, etc.

I like blink's message is a good start. What I want is SCS to make available the Cell plug-ins for VegasPro; of course, using Toshiba pc cell or Sony's brand------ which ever available. ;-)

just one thing please, as already stated, better video preview.

Hmmm, what about a version of Vegas that runs on a PS3, it has an abundance of video processing horsepower due to its cell processors. There are myriad reasons why it won't happen, but it would be cool.

In order of increasing complexity and cost to implement:

1) Change the default De-Interlace Method to Blend.
2) Change the default audio resampling to Best.
3) Native XDCAM EX Support.
4) Zplane's élastique time stretching in Vegas. Prosoniq's MPEX might be better but seeing as how a deal is already in place with Zplane that option could be difficult.
5) Some attention to Vegas's handling of alpha channels.
6) It's probably now too late in the day to fix 32bpc float so how about 16bpc (integer) mode? That should be more than adequate for most peoples needs and as it's new it wouldn't mess up any existing projects.
7) The usual suspects all lumped together. OMF, EDL, BWF Export.
8) OpenEXF and/or DNG Support.


Perhaps as the later suggestions are going to be expensive to implement and not appeal to everyone they could be offered at an additional activation cost.

Bob.

6) It's probably now too late in the day to fix 32bpc float so how about 16bpc (integer) mode? That should be more than adequate for most peoples needs and as it's new it wouldn't mess up any existing projects.
IMO, it's not really broken so much as confusing and potentially difficult to use.

It's unintuitive/confusing that levels will change between 8bit and 32bit projects for some codecs (and not others). The logic for that isn't obvious. Now the reason to do it would be to make linear light compositing correct, but then it would make more sense if all levels for each clip were converted into computer RGB. So it doesn't really make sense anyways.
But that's not the same as being 'broken' (unless you mean rendering errors), and 16bit integer won't really fix the issues or let you workaround them.

You know whenever these threads come up I think most people, including myself, try and think hard of those "would be nice" features and not ones really crucial to workflow.

Upon thinking about how I edit, here's what I'd like to see. I'm talking about AVCHD editing here but I believe this applies to all formats.

1. 100% CPU usage during previews, meaning better, faster previews. If CPU usage is not 100% then I should be seeing real time preview. All cores floored. This will enable me to edit faster, easier, and with better results.

2. AVCHD SmartRender so that my final render will be faster and of the highest quality possible.

3. Ability to easily select a 2-pass Blu-Ray compatible rendering mode where I can select bitrate. When I select "BD compatible" setting DVDA should accept the resulting file with no rerendering.

4. No problems rendering AVCHD with quad cores. I don't have a quad (yet) so I don't even know if this problem absolutely is platform independent but since more than a few have said they have this problem I assume it is actually an issue.

5. How about a good, easy to use deshaker plug?

Those 5 things I listed would make Vegas a pretty unbelievable NLE for me. I'll love it and use it anyway but while the thead is here I thought I'd put in my thoughts.

- Mark

"The logic for that isn't obvious."

Not that I want to derail this thread but what is the logic for this?
None of your articles explain the logic, they say what's happning but no word on why.

"but then it would make more sense if all levels for each clip were converted into computer RGB."

Now I'm even more confused, and I thought I had this under my belt.
Wouldn't it make more sense if 32bit worked the same as 8bit. 8bit is NOT computerRGB in Vegas.

To explain, I open the exact same video file in other apps and the scopes there read the same as they do in Vegas. Rendered output is the same. I switch both apps to 32bpc (float). Vegas gives a different answer compared to 8bit. The other apps give the same answer as 8bit.

Bob.

The concepts are:
1- If you want to do linear light / optically-correct compositing, all the levels have to be computer RGB. (Though this is violated because some codecs like the Sony Vegas DV codec decodes to studio RGB.)
2- The intention is that you pick 8-bit or 32-bit when you start the project, and don't switch between the two. (But obviously, some people would like to work in 8bit because it's faster and then flip to 32 bit for finishing.)
3- In 8-bit, you run into the passthrough problem described below. So that is why studio RGB is used.

Wouldn't it make more sense if 32bit worked the same as 8bit.
Yes!

8bit is NOT computerRGB in Vegas.
That's right.

But it can be useful to have a mode which would make it work that way.
(Though it creates complications.
If you convert everything to 8-bit computer RGB, then you'll clip illegal values. But when you're doing passthrough at the same time, e.g. when DV and HDV material is copied over instead of recompression+rendering, then the resulting footage will jump between illegal values clipped and illegal values not clipped.)

I love the “REAL rumors”

1. Corner pin tracking
2. Tracking
3. Grid warp
4. an Alpha channel on page roll transition or option to switch highlight off

Come Sony Vegas show some real rumorse for no 4

Ok, my long Wishlist:

WORKFLOW:
-Track lock button.
-Improved Prerender File Management (A simple Ripple should NOT delete Prerender , Add a Video Track should NOT delete prerender… etc).
-Ability to choose attribute when pasting Event Attribute.
-Ability to choose Video & Audio tracks (not necessarily adjacent tracks) when adding clip from Trimmer to Time Line.
-Video Preview when adding FX to clip in Project Media window.
-Add to the Event Pan/Crop window, the same loop/move tools of the Track motion window.
-Ability to display Markers on ALL Time Line (fx, generated media, pan/crop, track motion).
-Multiple Event Trimming (Like Liquid Edition or FCP).
-Ripple Edit currently DONT work when “Start, End or Lenght” are changed in Edit Details Windows. Please fix this.
-Ability to enable draw Wave Form & Frame Event SEPARATELY (in preference).
-Add the “Sync Cursor” to generated media.
-Add the internal option “Show Unquantized Event Start/End” to the View menu.
-Add a “Goto” option in Edit Detail window for Event, Markers and Regions.


VIDEO :
-Smart Rendering for AVCHD files..
-“Region” Filter (like Edius) to apply effect to only a zone of video (caution: this is not the same thing as Bezier Mask + Filter). Example: This filter allow to blur face with only one video track.
-Individual Photoshop Layer Import (like DVD-A).
-Keyframable compositing mode (Ability to switch to different compositing mode with an envelope).
-Native Render TIFF or TGA Image Sequence (script is too sloooooow).


AUDIO:
-Audio Event FX (like CD-Architect, this is a very useful feature).
-Velocity envelope for audio.
-Pitch envelope.

SCRIPT:
-Scriptable Trimmer.
-Scriptable Ripple Edit.

i'm with rosebud.....

leslie

5. Velocity event for audio.... how could I forget….!

thanks Rosebud

More than anything else, Vegas needs a plug-in API with access to sufficient functionality inside Vegas, including access to multiple video frames.

With that, most of the wish list items could be taken care of at no cost to SCS, and in a fraction of the time it would take SCS to develop them.

Again:

AAF, OMF, BWF export.

What could be done with After Effects, I don't care in Vegas.
I want SCS to finally lighten up and propel Vegas in the "big leagues". Everything's already set except all of the above... :(

Just fix the Quad core rendering bugs and the memory threading issue form 8C.

If 9 had ONLY that new fix (an nothing else),...I'd pay the upgrade fee.

Ok,..ok,..I want more AVCHD encoding bit rate options. Right now, it only encodes at the exact same specs that Sony AVCHD consumer camcorders record at. (is SCS riding off some kind of Sony MPEG liscencing fee umbrella for specific Sony encoding specs?)

That's it. I just desperatly desire that threading issue resolved once and for all.

CT

My wish list is short:

-Work with MPEG 2's in 64bit! So I don't have to convert everything to AVI.

-include some nice New Blue (or other brand) effects and transitions like in MS

Fix 8.1!!! Please Sony!!!!! =(


thanx,

ice

AVCHD 1920x1080 in the 64 bit version - with no bugs please - and a little higher bit rate option.

Support for CUDA processing of AVCHD mentioned above.

64 Bit DVDA

These are the only 3 things I want and I would be a very happy camper.

Improved ProType Titler. Currently it is too slow, has a silly interface, and keyframes are almost impossible to use accurately.

PAL Colour Bars and bars with 1KHz test tones, please.

Ability to lock tracks (as others have suggested).

Let's have a Vegas Pro pack with Cinescore and Sound Forge included.

I'd like to see improved support for AVCHD files; perhaps even the use of automatic proxies that would be generated when clips are added to the timeline, but use the original source files to render the finished movie.

To the effects tab I'd like to see a film looks filter, like Magic Bullet Looks.

Autodetection of project properties when clips are added to the time line, but the ability to over ride if need be.

10. Make 32 bit plugins work in 8.1. It's not that hard. A plugin is a DLL, load it in a small 32bit wrapper. Have Vegas 8.1 communicate with the wrapper.