How much of this would be applicable to those already shooting 24P on the DVX100 or SDX900? Can you work up a version of the script that skips the convert-to-24P step for those users?

If you are shooting 24p you wouldn't need the script. As for the 'looks', right now the ones in the RC1 version would be a bit extreme for footage shot with the DVX100. I may work up some looks that are DVX100 specific at some point in the future.

Can't download it says page could not be displayed.
Come on I wanna try!
;-)

Any reason that this script is tied strictly to WinXP? Tried installing on my w2k3 server and says the script needs XP so I am not sure if W2k users are left out as well.

Any chance we can fix this?

Hmmm. I installed it on my Win2K Pro SP4 and saw no such message.
Tom

Ed,
I just tried the Fx - great.

One question. I tried to apply Jitter and on closing and reopening the Fx, it's back to Dust.

What do I need to do to make Jitter 'stick'?
Thanks,
Tom

Ed,

I tried installing it on my Win2k SP4 system, and got the following error:

"Module c:\winnnt\system32\dfsc.dll failed to register"

I tried the script anyway, and after I select the render directory and presets, I get another error message "directory does not exist."

Any ideas what's wrong?

Feel free to e-mail me directly at prolefeed_studiosATyahooDOTcom if you don't want to tie up traffic on the forum.

Thanks!

If you keep the "look" presets they are, well - preset. So if you are trying, for example, the Kodak 5279 setting and go into that and add jitter it won't "hold" unless you create a new preset and save it with the jitter in it and use that instead of the exisiting one. That make sense?

I am not sure if that is what your doing but it sounds like it.

THe Dll you mention is part of the frameserver, not part of the actual script. The DLL is supposed to self register, I am not sure why it isn't doing that . I will check into it.

The "directory does not exist." Edward can take a stab at but what used to cause it was pointing to a directory that does not exist...in other words you used to be able to type in a directory such as "Film look render" or whatever. But the script itself does not create the directory so you would get "directory does not exist." In the new version you are unable to type that in and have to use the directory with the browser window. Provided you do that there shouldn't be any error.

>>>Any reason that this script is tied strictly to WinXP? Tried installing on my w2k3 server and says the script needs XP so I am not sure if W2k users are left out as well.

Any chance we can fix this?<<<

THis version is not tied to only XP. It should install on any system that supports Vegas - Windows 98SE, ME, W2k and XP. It is possible you are trying to do a server install and it isn't reading your local machine id but I can't be sure. Do you have the install package on your local drive or on a server drive? That could be part of the issue right as well. I can't fix the install unless I know what is happening and in pre-testing it worked on W2K so my guess right now is it has somehting to do with a server, but if you could give a bit more details.

Shogo. The link should be correct. Please try again.

acidsex: I tested it on a Win2K system and had no problems. I did NOT choose custom as the installation type.

For the directory errors: Are they upon installation? Or upon running the script? If they are after running the script, I'd like to hear from you directly via e-mail. Also, make sure a render type AND render location is specified before clicking on OK. If they are during installation, I defer to filmy.

For all other installation errors: I defer to filmy - he graciously provided the looks and the installation routine.

Ed- I get the "Directory Does Not Exist" error also. It's when I try to run the script. I selected a render type, and browsed to a directory ("null" is the default"), and the error message pops up. Note that I had upgraded to 4.0e- seems like the same problem Tsunami had...

Yep, trying to install locally on my W2k3 server. I just get the message telling me that the script needs XP. I even tried to run it in compability mode and it wouldnt work. But yes, its on W2k3. Funny thing is FilmLook10a installed but not the latest one.

cyanide, e-mail me directly and we'll try to sort out the problem. I can't duplicate that error here.

acidsex, I just confirmed that installing the FrameServer option gives the errors on Win2K.

cool, glad I could be of help ;)

I have not used it yet but I didn't install the frameserver part, I thought it was the same one I got from Satish. If it's different and needed here I'll install it too. Let me know, please. I installed the program on an XP sp1 machine and installed without a hitch.

Thanks

Don

The frameserver is Satish's

Hi filmy,
"If you keep the "look" presets they are, well - preset. So if you are trying, for example, the Kodak 5279 setting ..."

Actually no I am not. I click Fx button, select SONY Film Look (Untitled), and it comes up with 'Dust' as default.

I open list, select 'Jitter', close Fx. Open Fx and it's 'Dust'.
I've tried all the ones in the list. They all drop back to 'Dust'.

This is a bug.
Tom

I think you are misinterpreting what you are seeing. You can add dust by picking dust from the dropdown box and adjusting the slider. You can ALSO add jitter by picking it from the dropdown box and adjusting the slider. You can also add the other options as well. If you adjust several of them, you will see that the settings are maintained individually. When you close the FX and reopen it, the box just defaults to SHOWING the first item. You can then select, say, jitter and see the settings you picked for that option.

What JetDV has said is Correct. I thought you were trying out the presets. When you pick a plug-in from the drop down all it does is place that plug-in onto either the media or the track (Depending on where your select it to go) with the default settings, you adjust them later. the *only* exception to this is if you pick a pre-built look, in that case the FX chain is loaded with the presets. HOWEVER - No matter what you do, even if you save a custom preset, the plug-ins will *always* show up with the default setting showing. This does not mean that the "default" setting is what is actually being used. It is a bit confusing but it has nothing to do with Edwards script or my looks.

And it is only the Vegas frameserver. If you need the Premiere or other NLE portions you should get the full package from debugmode.

And there should be a little dll fix up shortly for those getting errors.