Chris Young
Forum Replies Created
-
Great news! Have had to go back to 8.0c for clients to be able to see any timeline monitoring. Sooner the better I guess.
Chris Young
CYV Productions
Sydney -
Mike ~
Working fine here on 8.0c. After using the’ Selection edit tool’ you hold down the shift key and drag your transition to the front of one of the pre-selected clips. This will only apply the transitions to the start of each clip. Once you have applied the transition to the start of each clip keep holding the shift key down and now left mouse click / drag a transition to the end of one of the selected clips and if it’s done correctly this will apply the transition to the end of all clips.
NOTE: If you clips are butted up end to end on one track you must make sure each clip has sufficient overlap ‘handles’ to allow for the duration of the transition applied. If the clips have their full length on the timeline and are butted up together the transitions will still be applied but the process will ‘loop’ the ends of the clips as there is insufficient transition time left in the clips. Believe me it does work. As previously mentioned I normally only use this technique for repeating the same transitions along a track that has nothing but lower thirds / captions etc so obviously everyone’s experience can be different depending on what they are trying to achieve.
As one other post mentioned it can un-group any associated audio. In the final analysis it’s up to the editor to decide if this technique is useful in any particular situation. So like always you weigh up the techniques pros and cons and decide if it’s useful in your workflow.
Chris Young
CYV Productions
Sydney -
Working fine here with both 8.0c and 9.0 on two machines, one with XP and the other Vista. Just make sure you mouse placement is 100% accurate, right on the very edge of the clip when you apply the transition. Works fine, do it all the time.
Chris Young
CYV Productions
Sydney -
Mike ~
If I understand your request correctly I think you mean create a fade up from black to vision at the start of a clip and fade down from vision to black at the end each clip. If you want to do this with numerous individually separated clips on different tracks try the following.
First go to Options/Preferences/Editing and set your ‘Cut-to-overlap conversion’ to your desired fade duration.
Next use the ‘Selection Edit Tool’ and drag a marquee event over all clips that require the transition.
Next go to transitions and select ‘Dissolve’. Hold the shift key down and left button drag the ‘Fade through Black’ transition to the very FRONT EDGE of any clip that was part of the marquee selection. What you are looking for is a series of small squares appearing, the front one with a little cross on it. Now let go of your left mouse button. All clips will now have a fade up from black to vision, the duration of which is whatever you specified as you ‘Cut-to-overlap conversion’.
Repeat the marquee selection of all clips and now follow the same process but drop your fade on the exact back end of one of the clips. All clips will now fade down to black.
BTW this process works for any transition, also pasting event attributes such as color correction etc. I have used this method for lower third graphics that wipe in and fade off on many a TV show over numerous years, a great time saver. First discovered it with Vegas 6.0 but as far as I know it’s undocumented.
Chris Young
CYV Productions
Sydney -
Steve, David, Frank et al ~
Re v9.0. When I get a chance I will have a further play-around my end to see if anything obvious overcomes the problem. I doubt somehow as sadly it looks to be a genuine bug/issue. Just glad to see it isn’t system specific to any one of us. Sony will want to jump on this quickly because one thing Vegas is known for is its legendary stability and I would hate to see that reputation go out the window.
Til later then
Chris Young
CYV Productions
Sydney -
As and where Mike says. There are a whole bunch of options even down to no timeline frame icons at all. Creates a little less CPU demand not running the whole image strip like v8.0 and earlier.
Chris Young
CYV Productions
Sydney -
Think so! A few of us are stumbling across a couple of issues, see previous posts. This has happened before with new release versions. I seem to remember it was a very short time after v8.0 release that 8.0a came out which fixed most of 8.0’s initial problems. I guess… hope that Sony will jump on this one fairly quickly, they usually do.
Chris Young
CYV Productions
Sydney -
Steve ~
Haven’t nailed it down to anything specific but it seemed to happen after hitting play a few times and also a couple of times when just cursoring along the timeline. The timeline vision would freeze but the audio was still playing. Trying to activate anything after that was useless. It was the old Windoz three finger salute to shut Vegas down.
Have had to bail out of 9.0 and back to 8.0c as have jobs that need finishing. Unusual feeling Vegas lockups. Had more with 9.0 in two days than a year of 8.0xx. Hope they get it fixed soon!Chris Young
CYV Productions
Sydney -
Yes Len. Select the little ‘TV’ looking icon above your timeline preview monitor. If you have a firewire to baseband video output unit connected, camera, deck etc you should see your video on the external monitor. This of course assumes you have set your ‘preview device’ set to OHCI under the options / preferences menu. The quality of the video preview out will depend on the settings and image size you have set in the Vegas preview monitor. We are PAL here and find if we make the preview monitor 720×576 for 4:3 or 1049×576 for 16:9 we get a very good quality picture output even when the the Vegas preview monitor option is set to ‘Preview auto’. By disabling the ‘Scale video to fit preview window’ option you will find that the preview window will snap to fixed sizes when you enlarge it. One of the sizes will be a 720×480 if you are 4:3 NTSC and I would imagine 1049×480 for 16:9. By using the full scale set size you avoid Vegas having to rescale the video hence better quality. Now try your output.
Chris Young
Sydney -
John ~
The main reason we are on Vista 64 with v8.1 is that we are editing (and shooting) with 1920×1080 50mbit 4:2:2 MXF files from the Sony PDW-700 XDCam HD. These things chew up ram like it’s going out of fashion. With 8.1 we can allocate 5GB to Dynamic Ram Preview and get a few seconds of playback. Running v8.0c at 1080 we can only allocate 1024MB to Dynamic Ram, a second or so of playback!
I have now sorted the memory issue by creating ‘System Managed’ paging files on both the media Raid and the C: drive. I previously had these set manually to 9GB, 1.5 times the fitted amount of ram, which is 6GB. Since letting the system determine how much page file it required it has now pushed both page files close on 13GB per drive. Main thing though is the low memory warnings have gone and its freed up physical ram. Vista 64 is one hungry mother.
Another issue started cropping up with 8.1 suddenly stopping with a ‘Sony file interface COM surrogate (not visible) has stopped working’ error. Vegas would ‘hang’ and have to be Ctrl, Alt, Deleted to restart. Turning off DEP didn’t fix it so I looked at ‘Start-up’ under MSCONFIG and disabled everything other than system files and that fixed the COM surrogate problem. It’s now a process of elimination turning on Start-up items one by one until the problem raise its head again… you just gotta luv computers!?
Thanks for the replies anyway.
Chris Young
CYV Productions
Sydney