abstractfactory/maya-capture

Define custom saving behavior

BigRoy opened this issue · 1 comments

Problem

The maya.cmds.playblast saving behavior does not seem very reliable. For example I'd assume in the following code to have the second one failing because the file already exists, but it does not error out.

import maya.cmds
maya.cmds.playblast(filename="C:/my_playblast", forceOverwrite=False, startTime=1, endTime=2)
maya.cmds.playblast(filename="C:/my_playblast", forceOverwrite=False, startTime=1, endTime=2)

Though only this one actually works:

import maya.cmds
maya.cmds.playblast(filename="C:/my_playblast.avi", forceOverwrite=False, startTime=1, endTime=2)
maya.cmds.playblast(filename="C:/my_playblast.avi", forceOverwrite=False, startTime=1, endTime=2)

Now the second fails. The problem there is that we don't know upfront what the resulting file extension will be, also see: #51.


These problems are just as much present in capture at the moment.

Any ideas?

I think we should talk about biting the bullet and manage files and encoding ourselves via ffmpeg.

For those without ffmpeg, revert to the current set-up, which is flawed. And if it's available, enable the more advanced and improved usage.

That way we could start tacking #6 and other in-image decorations.