Here’s a newer version with my latest fixes.
Disables the OutputFile when multiple inputs are selected, and it now preserves the disabledness when the sticky settings load up multiple inputs.
Also, I’ve changed the name of the OutputDirectory control so that it won’t load old sticky settings, just in case that screws people up.
Cheers,
Hi Jon,
Sorry, but I’m going to have to admit defeat on trying to get the recursive directory scanning and submission of a combo of both individual image sequences and mov/mp4 files as Draft individual jobs into the queue!
Please see attached Draft plugin code. I’m pretty close, but there’s a couple of things I can’t get my head around. If possible, if you could help, that would be appreciated!
See attached for complete Draft plugin (as you need an additional file as well: “SupportedFormats.ini”)
DraftSubmission.zip (8.99 KB)
I have also corrected a few typos in your code, which I think are correct. (probably best to do a diff-compare of my code against yours…)
Outstanding issues:
1.Submitting multiple individual image sequences by the “Select by File” method works, but it fails to write the FrameList/StartFrame/EndFrame to the ascii job file
2. “Select by Directory” submission system successfully submits jobs into the queue, but the job name is totally borked and so is the “inFile” / “outFolder” / “outFile”. Not sure completely what is going on here, but the jobs that get submitted seem to be all the letters of the alphabet! (if you sort them once they are all submitted)
Mike
So I had a look at it, and made a couple fixes. I was still using the FrameString from the text box, which I’ve fixed. I think the only problem with your code was that you forgot to parse the filenames from the semi-colon separated string into a list, which was mucking out the output folder stuff.
Cheers,
Thanks Jon! Your fixes are good.
I gave the recursive directory submission code a few tests and for some reason, the dictionary to only track unique sequences is failing to de-dup the image sequences and so submits a Draft job for every frame for each image sequence! It works fine for the “MultiFileSelect” submisison process of yours. Must be something in my directory crawling code, although its not obvious to me at the moment…?
So that one was a real stumper, but I finally figured it out! The issue is that there were spaces between files in the semi-colon separated string of files your code generates, which was mucking up the sequence parsing stuff.
There’s a couple ways to fix this, you can change your call to ‘StringUtils.ToSemicolonSeparatedString’ to pass in ‘False’ instead of ‘True’:
fileNames = StringUtils.ToSemicolonSeparatedString( supportedFiles, False )And/or you can add a strip to the frame parsing function:
def ParseFrameStringFromFile( inFile ):
if inFile != None and inFile != "":
inFile.strip()
[...]I’d recommend doing both, just in case 
Cheers,
Yep, all sorted and working well now!
Thanks Jon!
Final version, with a tweak to the “outFile” to ensure it doesn’t pass thorugh an “outFile” when nothing has been entered, such as in the case of batch Draft submission mode.
See attached.
DraftSubmission.zip (9.02 KB)
Mike
Hi Jon,
I found 1 edge case which I couldn’t quite see where best to fix. Potentially in the “def ParseFrameStringFromFile”.
I have an image sequence with an in-correct file padding such as: [mike_000.tga - mike_2500.tga]
Not sure if this can be fixed?
Also, I have found that the “def ParseFrameStringFromFile” takes a really long time if you feed it a lot of image sequences; say 30 image sequences between ranges of 0000-1000 for each sequence.
Again, not sure if this could be improved?
Thanks,
Mike