Chris Young
Forum Replies Created
-
Janzki ~
Welcome to Vegas land
Deferring to what Gary said I am not sure if this is what you mean. You have a number of clips on a timeline separated by spaces and want to apply a standard fade up to each? Is this correct? If so this is what we do.
Go to ‘options’ then ‘preferences’ and select the ‘editing’ tab. Go to the ‘cut to overlap conversion’ time window. Lets say you want a fifteen-frame fade up on each clip. Adjust the ‘amount (seconds)’ time window until it shows 15 frames to the right. Hit apply and then get out of there.
This is assuming that all the clips you want to apply a fade up to are one track, that is virgin clips with no transitions on them. Use the ‘Selection Edit Tool’, the one that looks like an arrow with a dotted box around it. Drag a selection along the track selecting all the clips you that want fade ups on.
Next go to the ‘Transitions’ tab and select ‘Dissolve’ in the left menu pane. This will open up the dissolve ‘Preset’ pane. With left mouse button click, hold, then drag the ‘Additive Dissolve’ up to one of your pre-selected clips and place your cursor on the small blue triangle at the top left corner of the clip until you see three small white squares, one with a cross on it. Release your left mouse button and the ‘Video Event FX’ dialogue box will open up. If all you want are fade ups that’s it. Just close the dialogue box and all your selected clips will have a 15 frame fade up.
This select and apply method will work for almost any transition. You can of course select any of the available ‘presets’ once you have the ‘Video Event FX’ dialogue box open if you want something other than a plain ‘fade up’. You can apply a fade down to the end of all selected clips as well; just select the small blue triangle at the end of one of your selected clips when you drag the ‘Additive Dissolve’ up to the track.
If you have various clips on various tracks the same rule applies, just use the ‘Selection Edit Tool’ to drag over the tracks and clips you want.
If this is not what you want to do then I have misunderstood your request. Good luck!
Chris Young
CYV Productions
Sydney -
Well I am glad to see that I am not the only one experiencing these problems. Have been over on the Sony forum and more and more posts are popping up with render problems in V6b. Check out the thread ‘v6.0b hangs during render’ by GreenMartian. I tried Ed’s suggestion of turning off Media Manager and it made no difference, well not here anyway. This is on a clean install on XP Pro SP2, P4 3.2Gig with 2 Gig ram
As a continuation to my original post where I first mentioned render problems with V6b:
https://www.creativecow.net/forum/read_post.php?postid=111840123246648&forumid=24
Further developments, it may interest some. I have observed the following on comparison renders between V5d and V6b on the same workstation. I posted this over at the Sony forum on the ‘v6.0b hangs during render’ thread.
——————————–
Hmm! Guessed as much… something broken with V6b render engine.
A job I had which kept hanging part way through the render finally finished rendering once I set the ‘preview RAM’ setting back to 16Mb. Previously it was set at 1Gig. Something not right here for sure. Sony advise not to have this setting too high as, quote,
‘If you reserve excessive amounts of RAM for your RAM cache, performance may decrease’.
Now that this job is done and out of the way I thought that I would try some experimentation. Setting preview ram to 64Mb and re-rendering the job I watched ‘mem usage’ in Task Manager go to .907 Gig and it used between 50 and 100% CPU overhead. This is with the process priority set to normal and affinity set to dual processor for V6, which is standard. This particular job took 25.61 minutes to render. Wherever I used Scot Moore’s SMLuminance plugin the processors dropped to around fifty-percent CPU overhead, understandable, as this plug doesn’t support multi threading.
Next I did a ‘select all
-
Peter ~
You are dead right, it is a bit pricey but if you are doing fifty or so repetitive graphics for a regular show each week it has strength in as much as that you can work with pre-defined templates, just change the data and save. The reason I didn’t go for it is that someone can be doing all our race graphics, lower thirds, grids, results etc on one workstation while another operator is editing. For us weekly deadlines determine show delivery time and the more I can spread the workflow around the better. Two jobs being done at the same time is more efficient. I agree, given the time, you can do some pretty amazing titles on Vegas using a number of various different tools. But for pure speed you cannot beat a keyboard driven CG whether it’s in a linear suite or NLE room.
Chris Young
CYV Productions
Sydney -
Have a look at
https://www.caymangraphics.com/PowerCG_plus.html
I have tried their demo and it’s not bad. It appears as a plugin in Vegas We use Inscriber Titlemotion Pro and create a lot of titles off-line and then bring them in to Vegas.
Chris Young
Sydney -
Alex ~
First up today following Ed’s suggestion I dropped the ram preview to 16 and had another go. Well, well! This time it completed the render, and in 19 minutes. ‘Good’ me thinks! Set the ram preview back to 1 gig and continued to work on the timeline, setting up pan, crops etc and adding more material. Thirty minutes into the work and bang, V6 hung. I opened Task Manager and sure enough Vegas had consumed 1.6 gig of memory. I clicked okay to the hung app dialogue and V6 disappeared. But NOT in Task Manager. I opened V6 again and sure enough I now had two instances of Vegas running. The only way I could close the crashed instance of Vegas was to ‘end process’ in Task Manager. This is a pain as I need to keep the ram figure up to get any decent length ‘ram previews’ to see just how this job is going to look. Problem is if you do this Vegas just keeps consuming ram til it hangs. Always had V5 set to 1 gig ram and never experienced this problem. Am in the process of trying to find out at what ram settings this high memory consumption kicks in. In the meantime I guess I will just have to keep Task Manager open and ‘save’ and close down when the ram figure goes up. When the job is re-opened ram use is back to normal but slowly builds again as you work. At this point I guess I have to consider it to be a ‘bug’. Why? Because when I duplicate the workflow in V5 on the same job it doesn’t have the same problems.
Another interesting thing has happened with V6 that has never happened in V5. Sometimes when moving media on the timeline or placing it there I have had an ‘exception’ dialogue saying something to the effect of, ‘Unable to create backup veg’. When you check the details button on the dialogue the underlaying message is something like ‘Unable to find all media’. After this happens some of the media in the bins will now have blank icons and when clicked on will not appear in the viewer. Shut down and re-open V6 and all comes back to normal. Another odd one to work through!
Thanks for all the suggestions so far.
Chris Young
Sydney -
Ed, Alex ~
In the interests of keeping the initial post a half decent length I failed to mention that I did actually try a pre-render. It failed at the same point and also hogged the memory. I must admit that I haven’t tried reducing the ram figure to 16. In fact I went the other way and increased it from 1 gig to 1.5 gig. Ed, I will try your suggestion of 16 which from memory was the default setting.
As far as rendering in sections, well that would be very disappointing if V6 can’t render a sixty second TVC without falling over. There is something very screwy going on in V6 that isn’t happening in V5. Watching the performance monitor between the two is quite an education. Very different behaviour. It’s very interesting Alex to see that you have had similar problems. I haven’t tried an MPEG 2 render yet but it sounds like a related issue.
Long weekend here but when I get back to work I will file a bug report and send the error log off to Sony because whatever it is it needs rapid attention otherwise V6 is going to get a rep as a lame app. Something I don’t think any of us whish to see.
Having done so many one hour shows all rendered out of V5 with no problems it just came as an unexpected surprise. Will continue to investigate. Thanks for the replies, good food for thought.
Chris Young
Sydney -
Paul ~
Had the same problem here with V6 on WinXp Pro Sp1. Sony state that SP1 is the minimum required on XP. I finally got it installed with Microsoft SQL working but the outcome was a pretty unstable V6. It would hang the second I tried to use Media Manager. Bit the bullet and installed SP2 and the latest patches for Net Framework then reinstalled V6. Went smoothly and no problems since… Well not with V6 working but compared to V5 check out my post ‘V5 v V6 performance… go figure?’
Chris Young
Sydney -
Howard ~
If you use Firestore DV Converter from Focus it will join avi files without the need for long rerender times. My experience is that with DV files it will join files together at around 2.5 times real time (P4 3.2 GHz). It has a host of options as to what type of codecs/file types you want to use. Under ‘Options’ you select ‘join’, add your files and hit ‘Start processing’. Simple as that. Just look through all the options first to make sure what codec you are using. I select the ‘Sony DV software CODEC (Direct X)’ one for both encode and decode and I can’t see any quality change whatsoever. Demo available at:
https://www.focusinfo.com/products/firestore/dvconversionsuite/dvcsuite.html
Chris Young
CYV Productions
Sydney -
Thanks for that Ed. Most likely will upgrade shortly when I put V6 on our main box once the current jobs are finished.
Chris Young
Sydney -
Marc ~
Go to the following link and you will find a streaming video feed that was shot at NAB giving you a rundown on Vegas 6 and DVDA 3.
To view it you will have to register on the site just like when you first logged in here. It might give you some pointers and shortcut the learing curve. Seriously though if you give DVDA a couple of good goes the ability to do things will come pretty quickly. As T.D. said up until now DVDA 2 was okay but 3.0 goes a long way past it. The stream video will show you the differences.
Chris Young
CYV Productions
Sydney