This is an absolutely brilliant tool, one of many available at http://ockhamsbungalow.com/Python/

I use it all the time for adjusting and cleaning bvh motion files.

BUT, recently, it no longer works on a few parameters. In particular, V4 shoulder "twist" (I think there are a few others, perhaps foot "twist"...).

This is likely due to SM regularly mucking about with Poser's Python implementation.

Perhaps the mighty Ockham, or another of you generous Python-fluent people could have a quick gander at the code and point me towards what needs changing?

With thanks and compliments in advance...

If you're in P2012 I can't help.  If it's P9 I'll take a look. 

Old Emphasizer probably needs to be reworked into WX-Python anyway.

Does it give an error, or just nothing happens?

I'm in P2012 SR3.1 x64 W7, but doesn't that have the same Python implementation as P9?

There is no error, just nothing happens.

By the way, I had a little blip with your BVH mixer. If the existing file is too short, the script hangs while it's trying to add frames, and clicking cancel causes a crash. (This isn't tragic, as I can just make sure the project has enough frames.)

I would be eternally grateful if you could sort out Emphasizer. It seems to be the only decent tool for editing animations.

Okay, I'll assume 2012 is the same as 9.  I finally switched to 9, so I can test there. 

Some of those Vicky parameters are wildly indirect, involving a series of ERC channels among several different sub-CR2 files.  I don't know if there's any way to control those from Python. 

I'll modernize Emphasizer so it behaves well in P9 and we'll see if that's enough.

Quote - I'll modernize Emphasizer so it behaves well in P9 and we'll see if that's enough.

Brilliant news! One can ask for no more, and since it used to work in P2010, I might even risk getting a little optimistic that it might work.

And somebody tell SM to pull their fingers out. Emphasizer's functionality is really something that should be included in the basic product.

Okay, here's the modernized version.  (Same link as before, new script is in ZIP.)

http://ockhamsbungalow.com/Python/Emphasizer.zip

Aside from the change of GUI, I've only added one new feature to the script.  It responds to a change of figure or actor by re-filling the list of parameters, so you don't have to close and restart the script each time you apply it to another body part or another figure.

Haven't done a lot of testing yet, and I don't have any Vickies at all,  I really doubt this will make a difference for your original problem, but we can always hope.   At any rate it's "modern" now!

One feature that occurred to me while playing with it:  How about distinguishing between parms that actually move in this scene vs parms that are static in this scene?  Different colors in the list?  Would that be useful or just distracting?

Brilliant news!

I'll give it a thorough runout tomorrow.

And highlighting parameters that move would certainly be useful and not distracting in the least.

Thankyou from another Emphasizerer

Good news: it solved my V4 problems.

Bad news: it doesn't work at all on Miki4. (Old Emphasizer doesn't work either.)

Bug report - that doesn't actually bother me that much - error window pops up with the message:

Traceback (most recent call last):
File "C:Poser Pro 2012RuntimePythonposerScriptsScriptsMenuEmphasizer-WX.py", line 198, in EventCB
self.Status.SetStatusText('%s in figure %s' % (ActorName,FigName))
File "C:Poser Pro 2012RuntimePythonlibsite-packageswx-2.9.1-mswwx_core.py", line 16237, in getattr
raise PyDeadObjectError(self.attrStr % self._name)
wx._core.PyDeadObjectError: The C++ part of the App object has been deleted, attribute access no longer allowed.

If anybody is reading this with the new Poser, are there any new features that allow the kind of "Emphasizer-style" bulk editing that is essential to animators? It seems strange that I have to depend on the mighty Ockham's script to make basic edits, and if there is something it can't deal with I have to use another app. You can't expect me to make an adjustment like +10 to the same parameter on each of 400 frames by hand...

(Or is there any other way of doing this other than with an Ockham script?)

Huh.  Here's a link on the dead object error.

http://bytes.com/topic/python/answers/36433-please-hlp-msg-c-part-statictext-object-has-been-deleted