- This topic has 10 replies, 2 voices, and was last updated 5 years ago by Eric.
-
Posted in: Muster usage
-
16th April 2019 at 7:33 pm #17402
Hi Eric
No there isn’t any hard limit , frames are mapped to float values and can reach extreme high values . Could you give us further information like the render engine , the start frame , the end frame , the by frame , if submitting from console or web , and the error is getting back
17th April 2019 at 5:28 pm #17405Hi Leonardo,
Here was the response from the student:
Sorry i neglected to mention that I am currently rendering out of the Arnold Engine and I am submitting my projects from a console, we are told to copy our project folder to the server file where we link to in our programs. Ive also provided screenshots of what happens, keep in mind that it is the same project but refuses to go past one thousand frames.
I’m asking for more information to see he is getting a specific error or if the job just stays in the queue indefinitely.
Thanks,
Eric
17th April 2019 at 6:49 pm #17407Ok I see that the job is sent from the Maya connector. Could you submit it directly from Muster console and see if the same things happens ? Also can you send a screenshot of the chunks details of the job ?
17th April 2019 at 6:52 pm #17408sorry I read it wrong, those are just the maya settings, by the way the frame range set into maya has no effect because it’s override by Muster. Could you snapshot the submission panel for the job so we can see the entire settings of the job ?
17th April 2019 at 7:04 pm #17409I’ve run a simple test, just to be sure (even the issue sound a little strange, we may had tons of customers complaining if we were not able to handle frames more than 1000 😉 , and with a Maya Arnold job, using a frame range 1-1000 we correctly get 250 chunks and with 1-2000 we correctly get 2000 frames with 500 chunks. So, tell the user to check :
1) The chunk size is correct
2) The frames range is correct, from the result it seems like he types 1-2000×1000 , using a by frame of 100017th April 2019 at 9:56 pm #17410Hi,
So I met with the student and he is submitting the job through the Maya Connector. From what I could tell, jobs with frames above 999 are converted into scientific notation and submitted to muster. I cloned the ‘bad’ job in the Muster Console and changed the frames to 1000-24001n1s1 as an example and submitted it directly within the console. The new job was able to process the frames successfully.
Image:
17th April 2019 at 10:31 pm #17411Ok now it is clear.. the bug you are reporting has been fixed and its due to mrtool muster command Line tool converting the frames submitted with the old flags -sf and -ef to scientific format . Those flags are still used by the maya connector. The bug has been fixed in 9.0.9 so I assume you are on an older version..
-
You must be logged in to reply to this topic.