RODALSA

I'm back after checking out elk's suggestions. #1 The version I was using was 9.23 that I download specifically chosen to be "... for home use ...". When launched a popup appear allowing the user to verify that their use will be for home use or not. #2 The version elk provided me with was 9.23 labeled in its About box as "Licensed User: Unlicensed Software". No popup appears when the program is launched as noted above. This version is still installed in my system. #3 The currently installed version ( elk's ) does not "hang" with the transitions turned off. They turn off but turn back on. ThEn... BUT.... #4 #4 It does not allow the user to change only one transition to a different duration. I tried all of the Shift, Ctrl, Alt key combinations while clicking on "Apply" after changing the duration of the transition. Of note here is that the 'apply to all transitions' button is greyed out but when clicked on does exactly what the "Apply" button does. This seems to miss the point of transition control. I liberally used the "... for home use ..." version I originally had installed to use different duration times in multiple transitions. #5 I branched out and investigated the relationship between the time required to complete a transition duration change vs the number of photos in the show. I expected it to be a linear function and it was. Caveat: I researched the "cycle times" at 6 photos, 12 photos and 24 photos. Extrapolation seems logically OK to do to 48 photos which is in the domain of my actual usage. The Excel 2010 plot's linear fit to the data produced the equation; " y = 0.937 x - .174" with the fit parameter r^2 = 0.9995. An r^2 = 1.0000 indicates a perfect fit to the data. y is the cycle time. x is the number of photos in the show. Using x = 48, y calculates to 44.826 seconds. That Is not a long time to wait for the cycle time to finish but the set up time is large since I used 10 runs for the cycle time and averaged them to obtain the values used for the linear fit. #6 I then checked the effects of the number of processes ( N ) that windows was manipulating by running my 24 photo cycle test once in Safe Mode. N in the Safe Mode was 21. The number ( N ) in normal Windows was 122. In Safe Mode y was 19.75 seconds. Not in Safe Mode y was 22.253 seconds making the Safe Mode 2.503 seconds faster which may be significant. I'll not spend any more time on it. Again the setup time for testing the cycle time is large with the switching back and forth into and out of Safe Mode.

PhotoStage version 9.23 home use. 1. Pick a transition IF it has a black bordered rectangle that is filled with an orange color resting on top of it. 2. Click on the transition to "Select a new duration". 3. Modify the duration by 0.1 second. This is not known to be a "must do" but a programmer's options imply that it could save you some time later. 4. Click "Apply" 5. Observe the black bordered rectangle's color. It has changed to grey. This applies to ALL of the transitions in the project. You will, if you activate the transition by properly positioning the red cursor and pressing the space bar, observe that the transition does not activate. I have concluded that my actions following 1 thru 5 above have disabled the transition. What I seek is a direct and explicit way to reverse what you and I just did. I have found one way that appears to effect the reversal. I launch my browser (firefox). I then click on PhotoStage Taskbar icon and - Walla - the orange colored box once again rests on the top of the transition - all of them in the project. Going to a separate program to turn on the transitions is a very awkward way to fix this problem. Windows 7 Pro Service Pack 1 Dell Optiplex 990 RODALSA For me to believe is insufficient for you to know. - rodalsa