Create package file with same name as original file?

Started by mattjgerard, March 09, 2017, 08:53:45 AM

Previous topic - Next topic

0 Members and 3 Guests are viewing this topic.

mattjgerard

When I am saving out a package file, is there a way to force KS to fill in the name of the current document into the ksp filename field in the save dialogue box?

Again, trying to automate some things, and this would help very much. Or is this a windows 7 issue?

Thanks!

Matt

Will Gibbons

How much time does typing in the name you wish to use add to the process? Or are you batching many processes? Are you currently using scripting? Just trying to get an idea of your workflow and what you're trying to accomplish. I just personally type in what I want to use.

mattjgerard

For an efficiency nut like me, any time doing a task that is unneccesary is time wasted, and there have been many times where there was that one tickbox I missed and left unchecked that will cause an app to do exactly what I am trying to get it to. Moving from the macOS side of the world, I am wholly unfamiliar with windows 7 and its behaviors, so I just wanted to know if I was missing something stupid simple to make this happen.

To answer your question, yes, I am looking to batch process finalized KS docs. Part of the workflow at my new job is to create one single KS doc for each product, while there may be dozens of similar products in a single category. When done rendering with the render queue (thank you for that!) I need to make a KS package and archive it using our oracle DAM system. So, having dozens of KS docs to work with, I am more than willing to research a way of automating this process as much as possible.

As I stated in the other post you kindly replied to, I would use Automator on my mac to streamline this process, but as I am not finding anything similar in the windows world (yet) as  you suggested I am looking at scripting.

So, that brings us to this point- I would like the ksp doc created to have the same filename as the currently open KS doc. This make sense, its logical, there really isn't a time or situation that I can think of where I'd need to manually call it something else. Other softwares (photoshop, premiere, etc... ) and the behavior of pretty much everything in the macOS world auto-populates a Save... or Save As.... or Export action with the name of the current document. So, my question was mainly to see if there was a preference or setting somewhere that would force this to happen. If not, that lead me to my second question as to if this was a Windows 7 limitation or function. I understand there might be small backgound utilities that can run that can modify the behaviors of these dialogue boxes, and I'm open to looking into those as well.

Anything to save keystrokes and redundant actions is worth the time to me.

I'm not a natural at programming and scripting languages, and I will take your advice from the other post and start inquiring in that forum, but I am looking for something like this-

open item from user selection (open keyshot doc or docs)
tell "Keyshot" pause render
tell "Keyshot" *save package file*
filename = *current filename*
location=*current location*
tell "Keyshot" *close current item*
end tell

Now, the only other issue is that unless the  user uses the "Open" dialogue from the "FILE" menu, keyshot will close the current instance of keyshot, then forcing the user to start KS up again to open the next file, which is time consuming even on an SSD and especially off a spinning drive. And if mulitple KS docs are opened at the same time, KS fires up a seperate instance of the entier KS app for each doc. I don't understand why, but once again I'm assuming its operator error until I'm told otherwise:)

Thanks, and I hope this clears some things up!

Matt

Will Gibbons

I don't personally have a silver bullet solution for you. There are some here who've done some scripting automation and you'll likely find out more about that on the scripting thread.

One way I'd personally approach this is to make one KeyShot document to contain each product within a category or family of products until the file gets too large to handle. Sure cuts down on the repetitive nature of what you're after.

I hope you find a solution that works for you!

mattjgerard

That's a good idea, I've got a bad taste in my mouth about the scene sets and view sets, as I got stuck in learning the hard way how they worked, totally my bad for not reading about them, but it was a learning expiereince. I'll have to look into that as well, if there is a way to pull the name of the view set and use that as the package file. On my lunch break i will summarize what I'm trying to pull off and see what the programming peeps have to say. If they say it can be done with some work, I'll dive in head first.

Cheers!
m