one possibility is that you have made another layer.  This can be done by using the walk designer (as one possible tool) and it created a second layer.  These come in as Replace so that if a channel (the dial with the green dot) has a movement on the second layer then you can not move that channel on the base or lower layer.  To see if this has happened on the Windows Tab click that then make sure Animation palette is checked.  In the Animation palette window click the layers Tab which opens the window to show what layers you may have and what their names are.  If you have more then one layer called Base Layer then most likely you made changes on the extra layer and now the controls for any layer below that layer are locked.  If you only have one layer then you might have locked the figures channels by clicking the lock figure or lock object option.

For the hair why don't you use the female texture map?  As I understand V4 & M4, or La Femme and L'Homme can share the same textures and most female maps don't have hair.

Signal Scope for Poser P12/P13 (renderosity.com)

Here is the link to the Signal Scope and Signal Generator.  I had to break them apart as Poser will complain about a feedback loop when the compound nodes are first loaded and you hook them up as shown above.  I think people will find the scope very handy when doing work in the material room.

Do you have to upgrade from 11 to 12 then to 13, No.  Since there is no upgrade path from 11 to 13 it will cost $249.95 (just looked at store price).  If you upgrade from 11 to 12 it is $99.95 and from 12 to 13 is also $99.95.  Doing the 2 upgrades will save you $50.  Plus you also have access to version 12 if for some reason you find it helpful

And to make it easier to set and see how those Map Range Nodes work below is the next Freebie once I get it finished.

The Scope Ranges Node sends out a test/control signal that you inject into the shader and then it measures the signal coming off the shader.  Much like an Oscilloscope you find on electronic test benches  

Uploaded the Freebie now waiting for approval.  Above is Render with 3 Maps on the right.  I have the Map Range on the Torus going from 1-.45 then .45-.7 finally .7-1, which why it has that big spot in the middle.  Below will be the node setup.

Just to show the TO range can go from large to small.

I don't think you have to have a prior version installed just have the serial number to enter when it askes for it.  Been awhile since I last did that, but when you enter the serial number and Poser sees that it is an upgrade it will enable the extra fields in the box to enter the older versions serial number.

Neat script.  However there a problem not with the script, but with Poser.  Currently you can appear to change the values on the inputs of a Compound Node but those values are not transmitted into the working of the Node itself.  In order to fully change the input values you need to make a small change to each input manually in order for Poser to know that an input has a new value.  The bad part is that you cannot change it to the same value.  So in this case click each color chip and select a color just below the top left column and it puts in a color very close to what was shown.  This is also a problem in Poser 12.

There is a ticket in and it is on a list of fixes.  Right now they are working on getting 13.1 ready for the end of the month.  

DSON was written by DAZ in Python 2.7.  Currently Poser 12 & 13 use Python 3.7.  the two Python versions are different enough that 2.7 won't work in 3.7 without a lot of changes.  I believe the DSON script (or parts that it calls) are complied and DAZ is the one that has those source code files so it would be up to them to provide a new version to work with Poser 12 and 13.

The Back Ground Picture feature has always been very limited, which is why most people choose a background plane or other method to put in backgrounds.  Below is a render from Poser 10 using the Background picture the render was done at 1920x1080, whereas the BG picture is 1919x1085.  This was with AutoFit on.  Notice the sides have a border where the BG fails to meet the edges.  That is because the AutoFit puts the whole image on screen to the setting of the render dimensions, which means the vertical is shrunk by 5 pixels which means the sides also shrink by a couple pixels each.  Also, if the autofit was not selected then the picture comes in square as that is the default setting for the node is U_Scale 1 V_Scale 1.  

So the BG picture and render only work IF both are the exact same dimensions, otherwise you end up with the borders on the sides or top and bottom.  

here are 3 pictures in P13 with FireFly

This is Preview with Auto Fit not checked.  The image is 1919x1085, basically 16x9.

This is Preview with Auto Fit checked.  Notice if does not quite fit the Preview window.

This is the Rendered image with Auto Fit checked.  Notice it is back to being a 1x1 aspect ratio.  And when it is rendered in SuperFly it looks like the middle image.  So Fire fly does have a problem and I have put in a ticket for this problem.

However if you go in and mnually set up the Back Ground image to be the proper size and DON'T have autofit checked as listed above then Fire Fly will work.

Going along with what Shvrdavid says about needing a Map Ramp here is a picture of what ODF's setup above looks like with No Map Ramps, 1 and 2 Map Ramps.  This is something I have been working on for a slightly different project but was easy enough to convert for this use.

The left set goes from 0 to 100%.  The second set goes from 30% to 100%.  The third set uses 2 Map Ramps and goes from 30% to 50% in the range of 0 to 87 and from 50% to 100% in the range of 87 to 100.  Notice the outline in the ball and torus.  Just have a few bugs to work out and it will be posted to the Freebies section.

In fact checking the Autofit causes the picture to return to that 1x1 ratio format.

@Nerd that does not seems to work.

Not sure how you are setting up the background picture, but here are a couple of things to try.

1:  In the material room set the U_scale anv V_scale to the ratio of the picture you are using.  A 1920x1080 picture be 1.7777 to 1 1980/1080 or 16/9.  This keeps the vertical scale the same so the whole picture fits on the background.

2:  in the U_offset set that value to -.38888.  That is 1/2 the value of the decimal portion of the U scale above.  This sets the start of the picture to the edge of the render frame.

3: Make sure autofit is not checked.

You can render frames without it shrinking. Not sure exactly sure what you are doing, but it appears that Poser is defaulting to the settings in the Material Room setup for a BG Picture, which is a 1 to 1 ratio which is why the picture turns square.  If your Back Ground picture does not have to have every single pixel you might make the U scale a tab larger and have the two edges be cropped during the render.  Looking at your example picture losing a bit on the two edges won't effect things that much.

You should write up a help ticket for your issue and give them all the details about what problem you are having.  Poser Support (posersoftware.com)