StackShot

[Stas Yatsenko]

The program makes linear steps. This means that if you have distance between A and B equal to 100 , the program will make 10 shots with 10 steps beween shots. What I meant with nonlinearity is that focusing steps applied to camera lens correspond to nonlinear change on DOF measured in mm. For example, one focusing step in macro area moves focusing plane by only 1 mm, but the same focusing step near infinity moves focusing plane by several meters.

You are using StackShot so your steps are all linear. One focusing step is always the same, near point A or near point B. As I understand you would like the program to be able to calculate DOF in mm based on the aperture, resolution, sensor size and distance to object. We plan this feature for the future versions. The major difficulty is to get information about distance to object. To fully automate the process we need to get this info from the camera, but is not always availabe and if it does it is not precise.

[OLH]

I tryed the new beta but it totally crash the mac !!!
Reboot !!

Macpro 2008
32 Go Memory
Macos 10.6.6

[Stas Yatsenko]

Hmm... Old version worked fine and new version (2.0.16) crashes the mac?

[OLH]

Positive ! Kernel Panic at launch !


Interval Since Last Panic Report: 211072 sec
Panics Since Last Report: 1
Anonymous UUID: 44E4C6BF-98C0-48BC-BA27-67652FEBAD44

Thu May 19 18:44:56 2011
panic(cpu 2 caller 0xffffff80002cffbc): Kernel trap at 0xffffff80002c2778, type 14=page fault, registers:
CR0: 0x0000000080010033, CR2: 0xffffff8291ed4000, CR3: 0x000000015fde3000, CR4: 0x0000000000000660
RAX: 0x0000000000000008, RBX: 0x0000000000000008, RCX: 0x000000000ffffdb4, RDX: 0x0000000080000012
RSP: 0xffffff8291ed2d38, RBP: 0xffffff8291ed3dd0, RSI: 0xffffff8291ed4000, RDI: 0xffffff8048056864
R8: 0x0000000000000000, R9: 0x0000000000000000, R10: 0x0000000000000001, R11: 0xffffff80004edb0e
R12: 0xffffff8048055540, R13: 0xffffff80480555b8, R14: 0xffffff8047d0a220, R15: 0xffffff8047d0b220
RFL: 0x0000000000010202, RIP: 0xffffff80002c2778, CS: 0x0000000000000008, SS: 0x0000000000000010
Error code: 0x0000000000000000

Backtrace (CPU 2), Frame : Return Address
0xffffff8291ed29d0 : 0xffffff8000204b99
0xffffff8291ed2ad0 : 0xffffff80002cffbc
0xffffff8291ed2c20 : 0xffffff80002e202a
0xffffff8291ed2c30 : 0xffffff80002c2778
0xffffff8291ed3dd0 : 0xffffff80002053ba
0xffffff8291ed3e00 : 0xffffff80002029eb
0xffffff8291ed3e60 : 0xffffff800027374a
0xffffff8291ed3ed0 : 0xffffff80002c1dc2
0xffffff8291ed3fa0 : 0xffffff80002e2606

BSD process name corresponding to current thread: usb_scan_helper

Mac OS version:
10J567

Kernel version:
Darwin Kernel Version 10.6.0: Wed Nov 10 18:11:58 PST 2010; root:xnu-1504.9.26~3/RELEASE_X86_64
System model name: MacPro3,1 (Mac-F42C88C8)

[Stas Yatsenko]

We will check this ASAP and send you newer version to test. A bug report after a crash would help us too.

[OLH]

after updating in 10.6.7 I have no more crash

But

For moving the stack only the two "big step" forward and backward buttons work, the four others not (one step and middle size step),
the goto A and B buttons work
but when i launch a shot the stack do not move step by step , but the trigger realease the exact number of time and in the end it moves a big size wich should be to come back to initial position but witch is not because it hasn't move in the interval !!

hope it help
thanks again for the support

[Stas Yatsenko]

This looks like mechanical issue. We had some lenses that ignored small steps. Try to set bigger step between shots in the Preferences and see if this changes something or not.

[OLH]

it's not a lense it's the stackshot rail itself

[Stas Yatsenko]

Hmm.. We never experienced a problem when StackShot ingnores the steps. Please make three kinds of steps and then Report a bug from menu\Help. This will send us log file and your settings.

[OLH]

Bug repport submitted thx

[OLH]

- we have one very specific need taht would be to have two BIG STEP forward/backward buttons, that the amount could be set in the preference to advance a very big amout (several centimeters but really precisly) as we use different camera with diferent position of the focusing plan and we could go back and forth easyly from one to the other, that way

Most probably we will implement it that way: in the Preferences you will be set number of focusing steps for >> and >>> buttons. These numbers are now hardcoded. But you will be able to set >>> you amount and use it for big steps.

Still not in the last beta I have : don't forget it it's a great feature!

[OLH]

looks like it's when the size of the step is < 1mm that it doesn't work
but it works fine when you put the size in number of "microstep" even for very smal size
could it be because the decimal is not a "dot" 0.3 but a "comma" 0,3 in our internationnal setting, maybe ? or something else ?

[Stas Yatsenko]

Yes, I suspect this is such kind of error. We scheduled this bug to be fixed till the next version, please wait a bit.

[OLH]

Hi
thx for the feed back on the last bug, here is a new one.

the software don't "release" the control on the command box when exiting.

I explain
1- when i plug the control box to the computer via USB before launching HR, i just have a "PC" indicator on the box lcd screen, but i can't still control the stack shot via the box
2- when i launch HR on the computer, the box indicate "USB Control" on the LCD and i take the controle via HR, witch is OK
3- when i exit HR, i should regain the controle over the box going back to state (1) but it still stays in state (2) the box indicate "USB Control" and i can't control the box anymore !!
4- I have to unplug and plug the usb cable to go back to state (1)

I would expect to go back to state (1) and beeing able to control the stackshot via the box directly after exiting HR. It is very important for us to work properly as we constantly go back and forth from Computer HR control to direct box control.

Thx in advance

PS i also submited that as a bugrepport from HR

[Stas Yatsenko]

Thanks, we will check if we close connection to the box correctly.