time for those Vegas 7 wishes...

CDM wrote on 11/3/2005, 5:09 AM

Please post feature requests/comments ABOUT listed feature requests here. Please don't start getting into arguments which will deflect the attention away from this list.

Mine:

Editing / Workflow:

- pencil tool for envelopes
- eraser tool for quick deletion of material
- slip tool that would slip the material inside the event so that the left edge stays put, but the right edge moves with the slip - essentially allowing for the start material to be changed but the end of the event stays the same.
- an auto-quantize feature which would differentiate between editing audio and editing video. Quantize always on with video. Quantize off for audio (unless you want it)
- Ripple edit: can someone tell me when I would want the following to occur?

aaaaaaaaaaaaaaaaaa cccccccccccccccccc
bbbbbbbbbb
dddddddddddddddddddddddddddddddd

why, when I trim event "a" back, does event "b" move too? I know you've explained the "logic" of this, but I don't see when you'd ever actually want that to happen? I would only expect items that end after the event I'm trimming to move. Furthermore, if the situation looks like this:

aaaaaaaa
bbbbbbbbbbbb

and I trim "a" back, b doesn't move. Why? and again, why would I want it to anyway?

- Trim Silence feature
- apply non-realtime effects preview that would play the event in context of the project.
- a "consolidate events" feature, for comping vocals or voice tracks. Instead of rendering to a new track.

Global Behavior -
- mono button on Busses
- True solo behavior (solo=solo, no pre-volume effect sends in the solo mix!)
- a find and relink right-click context option in the Project Media for offline media.
- previewing on an External Monitor still drifts for me. Not by much, but when playin back for more than a couple of minutes, I need to hit stop and start again to reset sync. Sync is fine with WSD.
- track freeze feature
- the ability to lock events but still make them trimmable, asr fadeable, etc.
- extract entire cds with regions.
- save and trim as .veg (trims all surrounding events, preserves envelopes and effects, flushes media pool, and moves new selection to beginning of project and saveas as new nestable "scene")
- Keyframe style effect automation
- VU meters
- Pitch envelopes
- while you're at it, time compress expand envelopes... :) Oh, and BETTER time compression.
- drag and drop effect chain from one track to another
- lockable track heights.
- the ability to save snapshots and copy snapshots from the trimmer view
- a "Force Relink" button in the Project Media view that would bring up the offline media dialog so you can search and relink with local media instead of media that might be on a network drive - this would be very helpful for entire projects that get copied across a network but still link back to the network path like \\cdm\projects\ etc.

more to come. I'm sure.

thanks for listening.

Back to post

Comments

MH_Stevens wrote on 1/10/2006, 11:50 AM

The need to "zip" a veg file with a simple tone as needed in the last VASST competition made me wish Vegas has a simple internal tone generator.

Wes C. Attle wrote on 1/11/2006, 8:32 AM

Reply by: DSE
Date: 1/5/2006 3:28:54 AM
....
As far as the rest of Peter's intermediate request,
only the HDV should be turned into an intermediary,
no other media type should be.

spot, thanks for the advice. I can't agree with you more after testing. Do you happen to know how the Print to HDV/mt2 works in Vegas? I was thinking that it renders to Cineform avi and encodes to mpeg/m2t, much like Vegas renders to DV and encodes to mpeg2 simultaneously you Render As DVDA MPEG2 directly from the timeline.

So my thought originally (until I tested) was to render my entire project to Cineform AVI just once to have a top quality source to encode from to multiple formats. The project had HDV, DV, and high-res JPG sources and needed to be rendered to m2t/HDV tape, DVDA friendly mpeg2, DV-avi, and wmv. So I thought rendering to HDV quality AVI which I could then encode to m2t, and the other formats would allow me to render the AVI in best quality once then encode to mpegs and wmv.

In the end, I could not print my project back to tape or save it in HDV resolution for safe keeping and best possible presentation. It would have actually taken weeks. But the DV render was fast and all formats looks real pretty. I just wish I could have an HDV resolution copy of the entire project for future use.

Coursedesign wrote on 1/11/2006, 8:37 AM

I just wish I could have an HDV resolution copy of the entire project for future use.

So buy a hard drive at the next local electronics store or online sale. 160GB Seagate for $49 or whatever is available this week.

That is the least expensive way, and you can even have all project files together (which you couldn't on an HDV tape).

David Thiel wrote on 4/8/2006, 4:46 PM

please separate the properties of titles from the text!
I might have a couple of dozen title clips and the client wants blue/shadowed text. I want to change the color and shadow properties of a group of selected text clips without changing their text.

there are lots of ways to do this (see layout and word processing programs)
Also, why is the text window not sizeable? My screen is big, why can I see the project window where I am typing?

Fancy text would be nice but basic text stuff should just work better.

TheRhino wrote on 4/8/2006, 8:21 PM

I have been a registered Vegas owner since Version 3.0, and have been happy with the improvements made to VV4 and VV6. [VV4 - advanced color correction, VV6 dual processor support.] I skipped VV5 because it did not add enough features that I personally needed at the time.

I will likely upgrade to VV7 if it continues to offer better multi-processor support and/or the ability to save, organize & maintain my custom presets.

The longer I use Vegas, the more presets I establish for all of the effects and tools. Mainly, I would like to be able to organize these presets more efficiently and also be able to store more of them [Vegas is currently limited to the number of presets you can save.... real bummer....] The ability to transfer these presets between computers, or save them along with a project would be a great asset. Sometimes I rework a project years later, but all of my custom presets have changed or I am working on a new computer. It would be great to have a more efficient system!

SO HERE IS MY LIST

1) Better multi-processor support for all rendering codecs [as noted]

2) Efficient method to save, organize and transfer custom presets for all Vegas tools and settings [as noted above].

3) An ongoing text-dump of changes that have been made to a project. Sometimes I pickup a project after working on many others, and forget where I left off. It would be nice to quickly scan a text message and remember the last 10 steps I performed...

4) Better Velocity Control - others have made comments here... a preset for 0%, ability to not move the entire timeline by anchoring certain points, etc.

5) Stop Motion Capture

6) More control over credit rolls and text in general - too often I have to use 3rd party tools whenever I want something to look right...

7) An AUTO color-correct & contrast tool much like what DVDa has under "Crop & Adjust". Sometimes DVDa does a better job color correcting pictures used as menu buttons, than I have done in color correcting that particular scene in Vegas. This could save me time if Vegas did a quick auto-color correct first, and I came along and polished the areas where Vegas missed it.

PixelStuff wrote on 4/9/2006, 12:44 AM

I agree with Padre that the biggest downfall to Vegas is the slow rendering times compared to the competition. When trying to convert Final Cut Pro users over to Vegas that has basicly been the only reason that they gave for not giving in. :-)

I also agree with BeerAndChips on the motion tracking feature. I've formaly requested that over the last 3 versions and so far nothing.

Third, 64bit OS support, preferably across the entire software line, but definitely as each new version is released. I.e. WindowsXP x64 was released spring of 2005 so any new Sony versions released more than 4-6 months after that should be 64bit native. At least that should be the rule for high end media apps.

Forth, I think the full manual needs to be the help file. Rather than the help file being a slimmed down version that just tells you what the tool is. Give us a context sensative help (as it is now) but with the extra info normaly found in the PDF. And the manual needs to include some basic technique help for newbies. For example the help section for the compressor would have a description of what the compressor interface does. Then what a technical description of what a compressor does to the audio. Then some examples of when or why a compressor might be used.

1 … 5 6 7 8

of 8