Timothy Duncan
Forum Replies Created
-
Scenalyzer is by far superior to Vegas capture. Now, if only you could drag from Scenalyzer directly into Vegas after being able to so quickly identify the shot you need…
I use Scenalzyer all the time especially for it’s additional features, such as archiving, and also file splitting and joining.
The only time I use Vegas capture is when entering advanced capture info for batch capture lists. If you ever want to re-capture anything in Vegas, you MUST use ADVANCED capture, because crash capturing does not capture with correct time code (it is 16 frames off). This means that every shot you might “re-capture” will be 16 frames off.
You can, however, recapture any Vegas projects that were originally captured with Scenalyzer.
td
-
Sure — you can apply FX to the whole group. Just put the blur FX as a track effect on the parent track and then inside the Blur effect, click the little triangle at the bottom left of the timeline (within the FX window). This toggle the FX between PRE and POST, and will apply the blur to all child tracks beneath.
td
-
Mark — I saw a similar weird issue like this during testing of V6. What version are you running? Make sure you are running the lastest release (6.0b).
Here’s a solution for you: In your preferences, go to the “video” tab. Make sure “Use external video capture application” is checked, and then click the “browse” button and navigate to VidCap50.exe (in your Vegas 5 directory) and select it as your external capture app. This way, you can launch VidCap 5 and get your work done.
Let me know how it goes for you.
td
-
[Chris Young] “Would you then suggest that for PAL one would look at 655 x 576?”
For Pal, use 786×576.
td
-
You will find that most others do not properly handle the 23.976xxxxxxx frame rate, and thus you will see just what you have described, so you will need to use image sequences in Vegas to avoid this issue.
Native square pixeled video in Vegas is 655×480 and this can easily be converted to 720×480 (Vegas handles aspect ratios very well).
td
-
FCP will import Vegas DV AVI files without issues. The difference you will find is with the video levels. Vegas uses video based level mapping into RGB color space and Final Cut uses computer based levels.
You can adjust with CC in FCP as needed. The best thing to use (if the project is DV) is a DV AVI.Side note: I convert FCP projects to Vegas on a regular basis for finishing for many of my clients. Vegas can read all files that FCP can, and can read the files via networking right off of a Mac. To put it simply, Vegas is like running Motion and Sound Track directly in the editing timeline without having to bounce out, and giving far superior sub-pixel rendering much faster.
td
-
The problem is because of AE and how it writes AVI files. You will have to use image sequences from AE because Adobe chooses to round off the 23.976 at only 3 decimal places. (It actually goes many more decimal places than 3 and Vegas uses the more accurate math).
You might also consider 655×480 using square pixels as Vegas actually likes this better than 640×480.
Are these all computer generated? What’s your source and also what is your final delivery or destination?
td
-
Just make sure you are rendering to the same format as the original footage. (24P or 24PA). You indicated it is 24PA (2:3:3:2). It should be a super quick render if the footage is not being converted and you are not doing any FX to it. You can take a look at the source clips in the Project Media to see if it is “Advanced” pull down or not.
Also — you may want to take a look at Excalibur. It could add a couple of hundred new automated tasks to your toolbox. Excalibur is the original scripting plugin for Vegas that brought multi-cam ( more than two years ago). Real-time camera switching is now possible in Vegas 6.0b thanks to Excalibur (Sony added this feature at Excalibur’s request to further enhance the existing multi-cam). Plus — you get all your camra angles added as “takes” so that you can swap them out on the fly quickly and effortlessly. You can monitor up to 25 cams at once, plus bounce back and forth from your line cut to the 25 cam view, and also get tally updates. It’s definitely the best multi-cam tool available now for Vegas.
I find it interesting that so many others have followed Excalibur’s lead. Pinnacle added multicam to Liquid, so similar to Excalibur it’s eerie. And look at Apple, touting multicam as a huge new feature for Final Cut. Thanks to Excalibur, I didn’t have to wait for the others to catch up as I’ve been editing multi-cam events with it for quite some time.
Take a look at this article:
-
Very good points Chris. I agree that V6 has a few more issues than V5 did. But most for me seem to be related to the Media Manager. I choose to leave this turned completely off most of the time, only enabling it with limited database usage on a per project basis. My stability is almost as good as V5 with this turned off.
My recomendation is to limit the size of your databases, and only open the ones you need. My system has never been able to open but about half of the files on my hard drives without crashing during an “import” to the databse manager. Sony is aware and they are working diligently on fixes for this.
td
-
Another easy thing to do is to nest the slo mo clip as a separate .veg. This enables you to still make speed changes to the clip as a whole, but split it frame accurately.
td