I'm getting the same error message: "Directory Does Not Exist". I open the script and select whai want and tel it where to render the file and all looks well. As soon as I execute the script it gives me the error. After I click the OK on the error box A new video line is added at my settings and an FX plug I selected appears. Is the script supposed to initiate a render or do I still have to render as I do normally.

Is the dll updater for WIN2K or XP?

My sys.
Win XP sp1
Vegas 4.0d

Well I certainly wish someone getting the "Directory Does Not Exist" error could e-mail me an exact method to duplicate this. I have not been able to get this error and I've actually TRIED to do so.

Maybe I could be some help -

Just some questions that would help -

1> when you *first* load the script and run it do you set the render location? Or do you leave it at the "default"? (Which will say 'null') This will cause the "Error: Directory does not exist" pop up to happen.

2> If you have run the script before and set the location, have you moved the folder or deleted the folder? The ini file retains your settings so if you had a folder called "D:\output\" but either deleted it or moved it the ini file would still have the location as "D:\output\". Unless you pick a new location you will get the "Error: Directory does not exist" pop up.

These are the only two way that I know will cause the error. Now if you wanted to add on to the above - is your folder on a removable drive or on a drive that is not currently hooked up? If so than number 2 would apply because the ini file is pointing to a folder that isn't there.

1> when you *first* load the script and run it do you set the render location? Or do you leave it at the "default"? (Which will say 'null') This will cause the "Error: Directory does not exist" pop up to happen.

2> If you have run the script before and set the location, have you moved the folder or deleted the folder? The ini file retains your settings so if you had a folder called "D:\output\" but either deleted it or moved it the ini file would still have the location as "D:\output\". Unless you pick a new location you will get the "Error: Directory does not exist" pop up.

1: When I first ran the script I set the folder location to my folder I render AVI's to. I have not moved or deleted any folders. I still get the error

2: Every time I run the script it doesn't see the folder location I set in the script, that is I browse select the folder, the folder path is dispalyed on the script setup screen. I execute the script and it produces the error.

For the hell of it could you do a test. Creat a folder on the same drive you want to render to and call it 'test' (without the '') Do this in Windows not via the script. Now open Vegas and run the script, choose that folder and try to render. Do you still get the same error? Now do the same thing but use the script and browse to a location and create a new folder. Do you get the error?

Filmy could you check your email? I sent you a message... Thanks.

The folder I selected was created with XP, I did not create the folder in the script. I just told the script which ine to use. I won't be back home until Saturday afternoon so I'll try you suggestions then.

When I used to get the directory does nto exist before, it was when i tried converting a MPEG-2 file on the timeline. DV never had a problem. Not all MPEGS had problems. It was sporadic in error.

Edward- can't wait to try it based on the original, but I can't get the download. Is the link broken or moved?

Thank you.

http://www.jetdv.com/scripts/RC3_VegasFilmLooks.exe

This contains the "Directory not found" error fix.

Any luck donp326?

Filmy I e-mailed Edward privately last Saturday with the results after he sent me a different script (RC2) to try. I still got the error but this one showed the directory the script created, it definately wasn't one I had entered. It added a whole bunch of stuff to the root I entered.

That may be a cause of the "no directory" error

JetDV have you seen my e-mail to you yet? Havn't heard anything.

I have the e-mail and will get back to you soon.

May have found the problem. I've sent Don another version to test. I'll know once I get the reply back from him.

Don has confirmed the fix was successful.

I can not download the script. Is it still available?

The current version on my website is: http://www.jetdv.com/scripts/RC2_VegasFilmLooks.exe but does NOT contain the "directory is not valid" fix.

what is this script doing that we couldn't already do?

Is it just me, or does DV NTSC photage that is pulled down using Vegas look a litlle too choppy? It looks more like webcam photage than film, IMHO. Actually, maybe film running at 15-20 fps, anyway. Not usable if you simply want to get rid of the "high gloss" fluidity of the original video and soften the motion a bit without sacrificing the overall quality of the image so much.

I seem to remember in a previous version of Vegas being able to render to progressive at 29.97 fps without introducing the choppiness that the pulldown adds. Now when I render to progressive it looks the same as interlaced, I mean, no difference whatsoever. It's as if selecting the option no longer actually flips a switch at all. I wonder if this is a bug. Maybe someone else could give it a try. At any rate, I gurantee that if it does work, it'll look better than if you actually add the pulldown, 2-3 or 2-3-3-2.

It also seems that the effects presets are all a bit extreme for just a basic film look, way too much grain.

Why couldn't someone just setup the effects chain in vegas to do the same thing that this script does?

I'm probably missing something...Somebody help me understand what it is, plz.

Thanks

I will try to answer some of the questions -

You can do it all without the script. For a lot of people it is just a time saver. Remember also this was based on Spots tutorial so it takes the steps he outlined and combines them into "one" step so to speak.

The "choppy" element is dependant on what the footage is like. If you look at a talking head it is very 'film like' and fluid. If you take fast whip pans to the Indy 500 you may have issues. You may have to work a bit on those sections. I know I have had a few things that I have had to play with - a firetruck moving through the shot and a pan up/down of tall buildings as two examples. On the other hand maybe it is just the film look itself that bothers you, it does bother many people so it wouldn't surprise me. Bottom line to me is always if you want real film look, shoot real film.

I am cutting a feature right now that was shot in 30p. Some of the pick up shots they shot at 30i so I am having to convert that to 30p. I am not seeing that 30i > 30p "not" working. In your case maybe try supersampling and see if that does it for you. I don't expect it will give ou much of a film look though.

As for the included looks - at the moment only one of them really included grain. And that is one that trys to emulate to grain of the Kodak 5279 stock. Did you try the basic film look? There is no way anyone could feel that is extreme. On the other hand, as I say in the "read me" - If you use the Panasonic DVX100 the looks may be far too extreme. This may also be true for some other cameras as well where the color curves are more "cine-gamma"-ish in camera. The 'release' version of the package will contain more looks that will hopefully fill in some of the blanks as it were.

I think the bottom line is that time after time people have asked about how to do a "film look" after they have already shot. This script makes it easier than trying to always explain a step by step process. The 'looks' save people time in playing around and give them a head start Keep in mind that one size does not fit all, but it seems too many people don't want to take the first step - so I sort of have done that for them. And others always said that you could not do a 'look" with Vegas - well, you can. It just takes a bit of time...it *did* take a bit of time. Now you can download a FREE installer that gives you a one step 24p conversion process that will add a preset look to the timeline, or a set of plug-ins of your choosing.

Did I mention it was free?

ok...

However, the choppiness I mentioned happens in both 'talking head' shots and high motion sequences...It's just more noticeable when there is more motion, because the change from frame to frame is greater.

I have no problem with the film look, I love it...

I submitted the original post having not exported anything with a 'filmlook' from vegas for a few months. After fiddling around with Vegas on a render it finally re-occured to me that what I had been doing to give my exports that 'filmlook' was to simply turn on the media level function called 'reduce interlace flicker'. This function alone makes a greater leap towards giving DV that 'filmlook' than anything else I've tried, including exporting to 24p, which adds the added choppy artifact that makes the phootage look more like it was shot at around 20 fps.

Best of all you don't have to do much to achieve it.

Don't get me wrong, I'm glad folks are out there making scripts and plugins for Vegas...I think I was just a little upset when I couldn't figure out what I had been doing to get the look I wanted, anfd then I did a search here for answers, and I felt like I was going in circles.

I'm sure you guys have tried using the 'reduce interlace flicker' switch. Try exporting to NTSC DV using this switch, and compare it to phootage that has been exported to 24p with no effects added. I gurantee that you'll like the results of the NTSC DV photage better. I did several tests a while back and I never reconsidered after. The only reason I would ever export to 24p is to save money when I have to deliver the finished product for a bump up to actual film stock or to produce a 24p DVD. I'm certain that the artifacts are a result of trying to playback something with a 24p cadence on NTSC equipment. Unfortunately I don't have the resources at my disposal to test this theory...I'll repost if and when I get a 24p DVD player and a TV that can play back 24p.

Thanks

My script was previously working fine, but now I suddenly have a new error I cannot debug.

"Error: Object reference not set to an instance of an object".

All my other scripts work fine. I have tried to re-install it and insure it says Sony and not Sonic Foundry, but still the same error.

Any suggestions?

Hard to say why you would suddenly be getting that error. I do have a version that will install in Vegas 5 WITHOUT the looks that is setup for Vegas 5 at: http://www.jetdv.com/scripts/FilmLook(Vegas5).exe