Thanks for the reply.
I believe that the issue with leaving the OutputPath blank is/was happening via the normal Rush script launch and not just launching it via jsx. It would be great if you want to email me your version offline.
thx
Dan
On Aug 8, 2013, at 10:42 AM, Victor DiMichina <victor@(email surpressed)> wrote:
[posted to rush.general]
Hi Dan. Notes below...
On Aug 8, 2013, at 10:27 AM, Dan Rosen wrote:
> [posted to rush.general]
> =20
> Hello,
> =20
> We are just getting around to a formal Rush submit script launched out =
=3D
> of AE. We are on Rush 102.42a9, CS5, Mac OSX 10.6.8.'
Which script are you using? I have a rush.jsx from Greg Ercolano and =
Simon Bjork from a number of years ago that worked well. I wrote up =
a tutorial on it for my users and you're welcome to have that, I can =
e-mail offline. =20
> =20
> I have found a few issues and have a few questions.
> =20
> - Leaving the OutputPath blank does not render what's setup in Queue =
as =3D
> advertised by Rush help.
Is this also the case when using the submit-afterfx.pl script manually? =
I haven't had this problem, but I also never tried it through a JSX =
in AE.=20
> =20
> - I am looking to add some features to a simple jsx script that was =3D
> posted to this forum. The script is great at adding the project file =
and =3D
> comp name to the Rush submit window, but I'd like to add more =
features. =3D
> Are there simple examples of getting a selecting comp into the Queue =
and =3D
> setting it's output properties? Any examples/help on this front is =
much =3D
> appreciated.
> =20
I think you might like the rush.jsx we have. It populates all of the =
fields. =20
> - Is there a way to add a custom menu to AE? like Nuke at the top menu =
=3D
> items?
> =20
This one is launched form file-->scripts-->rush.jsx
Best of luck
Vic
|