Random Ideas For Vegas 8.0 Feature List

TimOtholt wrote on 11/18/2006, 9:26 AM
A real 3d camera

Enough with 3d track motion. It's very limiting and unintuitive.

Give us a real 3d camera we can:

a. Set the focal length
b. Field of view
c. Depth of field
d. Mute and unmute the camera (supporting multiple cameras)
e. (optional) the aperture

How to implement it - it would be another "envelope" that can be added to the video bus track. Having multiple instances of this envelope would allow multiple cameras... and the topmost envelope that has an "unmuted" camera is the active camera.

Okay, that would be enough for me to upgrade for $149.95.

Oh yea, fix all the bugs already in Vegas 7.0b - like paste attributes, etc.


Comments

GlennChan wrote on 11/18/2006, 10:59 PM
1- I don't think that a video editor should spread itself too thin by implementing features like 3d cameras. For those few shots that require it, you could just go to After Effects or Combustion.

What would be neat is tight integration with a program like that... sort of like how audio integrates with Sound Forge (i.e. takes let you go back to earlier versions, etc.). Right click --> send to audio editor opens the clip in the editor.

2- It would be neat if Vegas could have performance like Discreet Flame or SGO Mistika. I don't know if this is possible, but I know Mistika feels ~10X faster than Vegas and runs on a normal gaming video card. The ~10X figure is not really an exaggeration; these systems can apply multiple layers of effects and still have real-time performance. They run on Linux, so this (may) give these systems particular advantages that Vegas won't have.

But even if Vegas can't have the performance of these six figure systems, implementing a strong base GPU acceleration may give Vegas a huge boost in performance. What if SMS were to rework Vegas' core to work off GPU-based effects, with adapters for VFW and openFX plug-ins (for backwards compatibility). Systems like Discreet flame are magnitudes faster than Vegas, but run on pretty pedestrian hardware- Discreet systems no longer rely on SGI hardware, and still get about the same performance (arguably faster).
Grazie wrote on 11/18/2006, 11:30 PM
Glenn, I like your wish for integration. Here's mine . .

I would like ability for Vegas to open up graphics in my preferred Graphics Editor. At the moment I have a 3 step, and then some on finish to get my work back into Vegas. Be great if the edited piece came back as a "Graphic-TAKE" - as per SF for Audio?

Wouldn't this be an easy thing to do? After all we do have it in DVDA: Options > Preferences > Video (why "Video" tab?) > "Preferred graphics editor"

. and why IS that TAB called Video, for a graphics editor preference?
bStro wrote on 11/19/2006, 9:33 AM
and why IS that TAB called Video, for a graphics editor preference?

Just to mess with your head, Grazie. ;-)

Rob
JJKizak wrote on 11/19/2006, 2:16 PM
Go to 64 bit so I can install 16 gig of memory.

JJK
vicmilt wrote on 11/19/2006, 3:16 PM
A "build beautiful movie" button.

Add your original footage to timeline - uncut.
Press button.
Come back in 15 minutes.

v
Tech Diver wrote on 11/19/2006, 3:36 PM
TRUE integration with third-party plugins. No more of this passing a single-frame nonsense as with Boris Red, etc.

Motion envelopes with Bezier points for true smooth control. Heck, make all envelope with Bezier control points like the rest of the world.

Peter
DGates wrote on 11/19/2006, 5:00 PM
Cup Holders.
GGman wrote on 11/19/2006, 5:09 PM
work with 10 bit uncompressed rgb log, 4k rez, 64 bit system 16 gb ram, linux, true plug in structure, dual quad (8 cpus)

gg
MH_Stevens wrote on 11/19/2006, 6:10 PM
And lets have some control over perspective ala Photoshop.

TeetimeNC wrote on 11/19/2006, 6:56 PM
Glenn and Grazie, I too like the better integration with leading tools like AE and Photoshop.

I also would like to see Sony make a pass through Vegas with the goal of further streamling the workflow. There are parts of the program that are very modal and require repeated open/close of dialogs to perform common steps. For example, typically I have to open the pan/crop dialog and effects dialog for every event. Why not put these two heavily used functions in a single dialog? Better yet, make it a single non-modal dialog that can stay open as you move from event to event.

Jerry
malowz wrote on 11/19/2006, 8:33 PM
psd layers, playback buffer adjustment, paste attributes with options ( filters, transition, pan/crop.. ) make the script icons not disappears, 10 bit editing, or processing at least, option to not disconnect dv preview on lost of focus, and the most important:

allow plugins to fully works on vegas.... (i.e. boris red)
Yoyodyne wrote on 11/19/2006, 9:42 PM
Completely agree with glennchan!
TeetimeNC wrote on 11/20/2006, 3:43 AM
Holy Cow - are disappearing script icons STILL with us in Vegas 7?

Jerry
farss wrote on 11/20/2006, 5:04 AM
Here's what I don't get about where Vegas seems to be heading.

The unofficial spin seems to be that "tape is dead", so no point fixing all that mundane EDL and capture stuff. Fine, Vegas is maybe 5 years ahead of the industry.
But if tape is dead so is video. Digital Film Acquisition is the thing of the future, it's here now, in 5 years when tape is really dead it'll be past being the Next Big Thing. So unlock Vegas, get rid of the video restrains, projects should be able to run at ANY frame rate, at ANY resolution. This isn't rocket science stuff. And while we're at it, can we please open up the codec support, DPX etc, etc.

And then we need to unclog the arteries, 8 bit simply doesn't cut it anymore. You can argue the technical merits or otherwise of that but fact is it's what the market is demanding. Sony are already pushing their 4K cinema initiative, invitations will be in the mail shortly, hope they invite Vegas to the party.

BrianStanding wrote on 11/20/2006, 6:46 AM
Yeah, the disappering script icon bug still pops up from time to time. I'd like to see that one fixed once and for all.

Here's the other things I've been waiting for for a while:
1. Storyboard
2. Interactive "Edit Details" window that automatically selects highlighted events, regions, etc. on the timeline (like Sound Forge's "Regions List.")
3. Nested folder tracks like in Acid.
DCV wrote on 11/20/2006, 7:39 AM
I completely second malowz:

"...paste attributes with options ( filters, transition, pan/crop.. ) make the script icons not disappears..."

Paste Event Attibutes with Options - This would be a nice workflow addition that would have saved me a ton of time on a project I just finished last night.

Why in the world are script icons still disappearing after all these years/updates/versions? Had it happen to me last night as well. Rescanning your script folder will bring them back - BTW.

If Madison ever finally fixes that bug we're going to have to have a serious party!

John
malowz wrote on 11/20/2006, 9:51 AM
;)
my boss (trying to move from premiere/matrox to vegas) complains:
i want to paste only the filters, not the transition @#$%!!!! premiere does!!!

and i have to agree...

and yes, the icons still go away sometimes... every day i use more scripts, more icons...

but this is nothing, the real problem to me is the plugins limitations... then rest is a "workflow glitches"...
Grazie wrote on 11/20/2006, 11:03 AM
Apologies if I got you wrong here . .

" . . complains: i want to paste only the filters, not the transition @#$%!!!! premiere does!!!"

But you can paste the transitions? You don't mean this huh?
malowz wrote on 11/20/2006, 11:37 AM
i mean it can paste only filters. copy transition i dint find useful..
dand9959 wrote on 11/20/2006, 12:28 PM
Heck, I'd be happy if they'd make the capture destination folder a part of the vidcap project rather than a global setting.


There. I requested it again.
GlennChan wrote on 11/20/2006, 11:05 PM
Paste Event Attibutes with Options - This would be a nice workflow addition that would have saved me a ton of time on a project I just finished last night.
Ditto. The FCP implementation of this makes sense. It pops up a window with options.

2-

If Vegas were to change its rendering core around (i.e. to heavily take advantage of GPU acceleration), then at the same time they might want to re-design it to operate at a higher bit depth and handle different color spaces better. What may be nice is:

2a- Do all processing in 32-bit float. Both GPUs and CPUs support this (except for older ATI cards, which only do 24-bit float). There may be a small performance hit depending on how this is implemented.

This will help fix the levels filter, which doesn't round numbers and clips things at 0.

The other nice thing about a floating-point rendering path is that it will support numbers that are out of range, so you don't get clipping when moving things from filter to filter.

2b- Convert all imagery into a single color space when rendering, and then convert it back out to the right color space on export. This will fix problems where people don't manually wrangle their color spaces correctly, between computer RGB and studio RGB.
It will also fix the problem of filters that are designed to work with computer RGB color space (which makes the controls weird and finicky when you want to work in studio RGB).

Even if Vegas didn't change it's rendering engine, some sort of automatic color space management should be done. Vegas, by default, should give you the right levels (which it currently doesn't).

2c- Vegas could also use linear light processing; this gives more accurate looking composites and dissolves (more film-like). It can do this by rendering everything in 32-bit float and by converting all imagery into a common linear-light color space. i.e. undo the transfer functions of sRGB, Rec. 601, and Rec. 709 material.

On the other hand, this (2a, 2c) may not necessarily be worth doing. Probably people's biggest concern is being able to add some nice graphics to their projects; add some production value to your projects. This can be done either via:

A- Make Vegas better at doing simple graphics work. i.e. it could use a better titler.

Set it up so that you can use motion video/backgrounds (with alpha) for lower thirds and such. Everything should be responsive and render fast.
It should take that much button pushing to get where you want.

B- After Effects or Combustion integration.
Tattoo wrote on 11/22/2006, 12:38 PM
I think the other Brian covered this, but it should be darn easy:

- be able to contract multiple tracks into one group for display purposes (and later expand it again by clicking on the "+" sign, just like Windows Explorer). Acid 6 already does this. So much nicer than giving up valuable screen space to a bunch of composited tracks for a special title or something.

Brian
MarkHolmes wrote on 11/22/2006, 4:36 PM
10 bit.
10 bit.
10 bit.

Did I mention 10 bit?