John Rofrano
3
COW Coins
Forum Replies Created
-
> and yes, the project was pretty much all edited in vegas
Unfortunately, I don’t have an answer for you and a quick Google search turned up lots of posts about FCP blowing up on EDL import with no resolution, but before you drive yourself crazy getting this to work, I thought I would point a few things out. The EDL Export in Vegas only supports the first Video track and Audio track. So if your Vegas project has more than one video and audio track this isn’t going give you what you expect. Also it only supports cuts and cross fades (dissolves). No FX or transitions of any kind will be exported so any color correcting or other processing will be lost.
I just wanted to be sure you knew this so that you don’t spend a lot of time getting it to work only to find that is not what you expected. Good luck.
~jr
-
I’m not sure I follow this workflow. If he has the camera and he wants to edit on his Mac, why does he need you in the workflow? I assume it’s just to capture. If so, how are you capturing? Firewire or Analog? Again I’m going to assume it’s analog because all Mac’s have firewire ports so why would he need you to capture via firewire?
If the above is true, it will depend on your capture device. Many of them have an NTSC/PAL switch. Just make sure you configure your capture device for PAL. Then in Vegas, use PAL project settings and place the AVI files on the timeline and render as Quicktime PAL (you are correct he’s going to want Quicktime files if he’s on a Mac)
It may be a lot easier to move your analog capture device to the Mac and do it all on his computer with his editing software. This way you are guaranteed it is in the correct format that his software is expecting. Again, without more details of why he needs you it’s hard to expand on a solution.
~jr
-
Actually, I’m one of the VASST Trainers 😉 and I’ve watched Jeffrey’s training DVD all the way through twice and then from time-to-time I refer to it for different situations that I might encounter that I know Jeffrey has covered and I’ve forgotten how to handle (cuz’ it’s tough to keep all this stuff in your head unless you use it every day).
It’s a great resource to gain a basic understanding of audio and how to use the various plug-ins that come with Vegas (i.e., Noise Gate, EQ, Multi-Band Dynamics, etc.) to control noise. The thing that I like about Jeffrey’s DVD is that he does this for a living so he’s using real-world examples of problems he’s encountered to show you how to fix them. I find it easier to learn when you can relate to the example like that and I always try to do that in my own training.
~jr
-
Dry refers to the unaltered signal. So if you were recording vocals dry, you wouldn’t add reverb or any FX. You’d just record the raw vocal and the add the FX later when you mix down.
Wet refers to an altered signal. When you record wet you would add an effect like reverb while you record so that its part of the recording.
When you encounter the terms wet/dry in an audio plug-in, dry refers the the original signal coming in and wet refers to the processed signal. If you have a wet/dry slider, that would determine how much of the original “dry” signal gets mixed in with the processed “wet” signal.
Does that make sense? If not, please feel free to ask questions. that’s how we all learn.
~jr
-
Hi Karl,
Here is what has changed between scripts and commands. Vegas wraps your entire script in an undo block. It can do this because all processing stops while the script is run. Because custom commands are always available as an extension while the project is being work on, you must declare an undo block yourself in your code whenever you change the project.
Try adding this to your code:
void HandleCommandInvoked(Object sender, EventArgs args)
{
MessageBox.Show("Script Start...");
string tNewFile = @"G:\project_TEST\00_Layout\avis\Sc062_S0004.00.avi";
MessageBox.Show(tNewFile, "tNewFile");
using (UndoBlock undo = new UndoBlock("Test Command"))
{
try
{
Media m = new Media(tNewFile);
}
catch (Exception e)
{
myVegas.ShowError(e);
undo.Cancel = true;
}
}
MessageBox.Show("Script End...");
}
This will stop the error that you are getting.~jr
-
Yea that does sound like interlacing issues where the field order is reversed. You might want to render the project as progressive just to eliminate it all together. This way it will be progressive on a progressive display and any DVD player will interlace it if it is connected to an interlaced TV.
~jr
-
I’m not sure why this isn’t working for you. I just tried it and it works for me. Did you press Add before you pressed OK?
You might want to look at TrackView.Zoom.MinTrackHeight. It’s already mapped to the tilde key (~) and also by double-clicking on the vertical scroll bar on the right side of the track view. Just use one of those two methods if you can’t get your other map to work.
~jr
-
Those beeps are because WaveHammer is in demo mode. If you have used it before, it has since forgotten that it is registered. The first thing I would try is the migration tools. In Windows go to:
Start | All Programs | Sony | Utilities | Migration Tools | Register Sony DirectX Audio Plug-Ins
If that doesn’t work try:
Start | All Programs | Sony | Utilities | Migration Tools | Copy Sony Plug-In Licenses from Installed Sonic Foundry Plug-Ins
If that doesn’t work try re-installing the application that you got WaveHammer with (Sound Forge or Vegas), and if that doesn’t work you need to call Sony Tech support. 🙁
~jr
-
Yes, the pillarboxing is just tiny strips. Most people would probably not even notice them on a TV unless you pointed it out.
~jr
-
Vegas does not place a visible time and date on a video. It only has a Timecode FX which must be manually added. If they were there before, they must have bene on the original tape, or you were not viewing them in Vegas. I have never seen this behavior in Vegas and I’ve been using Vegas since version 3.0.
~jr