Maya 2011 BUGS (Write Here)

#161

I don’t have this problem on Win 7. I’ve always playblasted to an image sequence and you’ve always had to set what file format you wanted in the render globals. I think the iff in the playblast option really just means playblast as an image sequence, and what ever your render globals are set to isfid what it’ll output.

#162

I think it’s more that Qt programs don’t use Quicktime’s API like Cocoa and Carbon apps. Nuke doesn’t have the prores options either. I don’t think it’s more Apple’s problem as much as the devs just not wanting to write a bridge for the format, especially considering that anyone really concerned with quality is just going to render to frames anyway. If H.264 was missing, that would be bad since you need to send draft stuff by email but how many people do you know put Prores playblasts in comps?

#163

I’m confused…

#164

weird. Don’t have the options in 6.

GOD. I’ve just crashed Maya twice in a row trying to add a camera but the menu twitched and brought the app down. grr

#165

For sure. It’s just my funky workflow but it used to be so nice and simple.

For final renders I certainly do render to EXR sequences…but for days, weeks or months before I pull the trigger on a final shot I’ve got an FCP timeline open (often ProRes) of my edit while I’m working a scene in Maya. And I like to spit out simple shaded or wireframe Playblasts of each sequence from Maya to get timings right. I do this over and over.

When the Playblast is set to the same CODEC as my FCP timeline then I can, as the project progresses, have a mixture of finaled sequences sitting next to WIP Playblasts with minimal FCP rendering. If I keep the names the same then I don’t even have to reconnect the media because the Playblast simply updates in FCP. You get the idea.

Now in 2011 I have to add an extra set of steps to get a Playblast into my edit. IMG sequences have to be processed with After Effects or Nuke into a usuable MOV. Since I don’t do much film work, if I use a MOV out of Playblast then I still have to convert the 24fps to 30fps.

#166

That’s a screengrab from NukeX 6.v1 32bits on 10.6.3.

#167

ah - I must not have installed the codec then. I thought it was installed by default. Sorry - I’m not much of a video guy

#168

Yup…having FCP 6.0.6 installed and an AJA or Blackmagic card will add all sorts of fancy CODECs to your menu (DVCPRO HD, XDCAM, etc…). And considering FCP 6 is 32bit I’m wondering if Apple still has some work to do. I haven’t bothered to buy the latest FCP so not sure if those CODEC versions are any different. But then again, I never occurred to me that CODECs could be either 32 or 64bit. SHow’s how little I know.

I’m wondering if a newer build of NukeX on the Mac is 64bit and if it would do the same thing as 2011 is doing by only showing a limited number of CODECs.

#169

Just noticed in the docs for the playblast command why this is; apparently it will ignore the settings in the save dialog, and use your image format settings from render globals. not sure why hey decided to do that, but they did. It should have it’s own settings in my opinion, leave render globals for real rendering.

#170

kevin - you can run the OS X version of Maya 2011 as 32-bit the same way as with other apps - get info in the Finder on the app and turn on 32-bit. See if that adds the codec.

#171

Yup…but I’d still have MOVs that were the wrong length and frame rate. Thanks though.

#172

It’s always been that way for me, what ever I have selected as the image format in the render globals has always been what the playblast ends up saving as.

#173

Has anyone else had a problem with increased render times and memory problems in 2011? I have a scene from 2010 that renders in 2:46 but the same scene with nothing changed takes 24.16, if it doesn’t crash from MR running out of memory.

It seems that the majority of the extra time is spent in the FG phase. Is there some new checkbox I’m not seeing?? :slight_smile: Thanks

#174

Hmmm…maybe since my render globals are set to EXR, Playblast gets confused. I’ll try that.

Yup…that’s it. Since EXR doesn’t appear as an option under the Playblast window, then whatever you choose gets output as an IMG. So you have to set your render globals to iff in order to get a Playblast that’s an iff. Set it to PNG to get a Playblast that’s PNG.

When you’re ready to really render out of MR, then set your render globals back to EXR.

Sure does seem these two things – Playblast and Batch Render – would not be interdependent.

#175

Playblast frame rate issue : Logged as #353533. We have reproduced it on Mac OSX/Windows and we’re looking into it.

Playblast in IFF format : Logged as #354458 - Playblast IFF uses file format from render globals, not from playblast options.

Mac OSX 64 bit codec : The list of codecs available on Mac 64 bit does not change even if you install additional codecs. If you have installed additional codecs for playblasting, you must run Maya in 32-bit mode. The QuickTime API that we use doesn’t give us access to the list of installed codecs on Mac 64 bit. It’s logged as #[size=6]356593, but I’m not sure what can be done for this.[/size]

#176

Nurbs curve > right click > control vertex = No vertices are actually visible even though the curve turns blue and the invisible vertices are there to drag if I randomly pull them without any visibility. Anyone else have this problem? If not then any idea what is going on? :lightbulb
I am on win7 64bit.

#177

does anyone know how to make a camera popup menu within a marking menu? I’m walking on eggshells every time I access the panel camera menu because it’s going to crash if I’m TOO FAST.

#178

Can someone please verify this hotkeys problem:

Maya automatically add (renew), without asking, all previously and manually removed default-hotkeys.

for example (hotkey editor):
Status Line -> SnapToGrid
“Curret Hotkeys”: X, x, X Relese and x Release. Just remove them, save, exit maya, get back into maya, all of them are again there!

Major bug for someone who is using many of own created ones. Now hes own hotkeys, has dual functionality with default functions that make the work impossible.

julius

#179

my custom hotkeys are working fine. You might have a problem with your preference permissions or something.

#180

Im searching for the reason since 2 days. :frowning:

Did you have removed the hotkeys like in example described?

julius