Re: [Nuke-users] Can I use 2D track for 3D Camera?

2012-09-14 Thread Howard Jones 
FWIW I've modified this today for the particle shot I'm doing and added depth 
as well as scene scale knobs,
so you can manually push it back/forward in Z. Also an option to auto scale the 
geo so as you increase the scene the geo scales the same apparent size in frame.


Also I found an 'addLayer {rgba.beta}' line in the last one so you should 
remove that if you dont use this version (same version name)


Cheers 

Howard




 From: Todd t...@nulightfx.com
To: Nuke user discussion nuke-users@support.thefoundry.co.uk 
Sent: Friday, 14 September 2012, 2:09
Subject: Re: [Nuke-users] Can I use 2D track for 3D Camera?
 

Basically I simply increased the scale until it looked right. I went by 
nothing in particular. I probably could look into more detail next time. 

Thanks everyone for your help.

Howard Jones  wrote:


Out of interest did it work as Randy says. The tracker2camera is based on 1 
unit as far as I can tell. So did it work with a straight match of units? I 
know I wrote it but it's like bread - I don't have to know how to make it to 
drop toast butter side down. 


Haven't not used it for a long time I've just realised for a shot I'm doing 
with particles it will give me a quick way of tracking the emitting geo in. So 
been a useful relook at an old tool for me. 


I don't think I ever sussed out object scaling properly but I might look at 
that as well again. Though of course it'll never be a 3D tracker. 

Howard

On 13 Sep 2012, at 23:50, Todd Groves t...@nulightfx.com wrote:


Thanks, Randy. I got it working. :)






On Sep 13, 2012, at 3:11 PM, Randy Little wrote:

You have to make sure you units in Nuke and Modo are the same. and when you 
import make sure the units are set correctly

Randy S. Little
http://www.rslittle.com

http://www.imdb.com/name/nm2325729/






On Thu, Sep 13, 2012 at 2:59 PM, Todd Groves t...@nulightfx.com wrote:



I found it. I just have to scale it dramatically to match the size of the 
shots needs.








On Sep 13, 2012, at 2:51 PM, Todd Groves wrote:



How do I scale the scene? The Camera moves in my 3D program, but only 
slightly; which means I need to scale the scene before generating the FBX.








On Sep 13, 2012, at 2:26 PM, Marten Blumen wrote:

Not sure why it doesn't work, I can see the camera moving here


On 14 September 2012 08:57, Todd Groves t...@nulightfx.com wrote:




Hey Howard,


The Axis moves, but the Camera doesn't move. Will that change if I use 
WriteGeo to generate an FBX version?










On Sep 13, 2012, at 1:18 PM, Howard Jones wrote:




HI Todd

Script below. Your track range is 953-987 correct?

Anyway I put your track into the tracker2Camera gizmo
Created camera using 'create camera' under the 'Translate solves'

That was it - worked fine, might even match your image. Use the latest 
Tracker2Camera (attached again)




The script below is set to HD as I dont know what format you are 
working in.

 
Howard





set cut_paste_input [stack 0]
version
 7.0 v1b38
push $cut_paste_input
Tracker3 {
 track1 {{curve x953 1192 1247.527466 1304.445923 1361.67395 
1420.560303 1482.739014 1548.128296 1610.351685 1671.486572 1732.383667 
1793.790527 1853.362915 1912.415894 1974.61438 2034.171753 2091.987915 
2145.516113 2197.037842 2249.268921 2301.771729 2353.022583 2401.169312 
2450.260254 2500.791992 2553.439941 2607.471924 2661.059082 2713.591431 
2765.387695 2819.274414 2875.749146 2933.259277 2988.799438 3042.455322 
3093.411133} {curve x953 818 819.5675049 821.9576416 824.9746704 
828.8840332 835.4890137 843.7455444 852.7792358 862.2110596 871.3128052 
882.1752319 892.2661743 902.6511841 912.3652954 923.1884766 934.8099976 
944.2409668 951.4041748 956.5293579 961.5074463 964.8376465 967.0097046 
968.0718994 968.6292114 970.2266846 971.1508179 972.5056763 972.8568115 
973.5623779 974.3269043 975.4362183 977.2075195 979.0283813 981.0758057 
983.494873}}



 offset1 {0 0}
 pattern1 {-104 -54
 104 54}
 search1 {-84 -77 84 77}
 track2 {1126 474}
 offset2 {0 0}
 pattern2 {-32 -32 32 32}
 search2 {-22 -22 22 22}
 track3 {1126 678}
 offset3 {0 0}
 pattern3 {-32 -32 32 32}
 search3 {-22 -22 22 22}



 track4 {922 678}
 offset4 {0 0}
 pattern4 {-32 -32 32 32}
 search4 {-22 -22 22 22}
 transform match-move
 reference_frame 953
 translate {{curve x953 0 55.52746582 112.4459229 169.6739502 
228.5603027 290.7390137 356.1282959 418.3516846 479.4865723 540.383667 
601.7905273 661.362915 720.4158936 782.6143799 842.1717529 899.987793 
953.5161133 1005.037842 1057.269043 1109.771729 1161.022461 1209.169434 
1258.260254 1308.791992 1361.439941 1415.471924 1469.059082 1521.591309 
1573.387695 1627.274414 1683.749023 1741.259277 1796.799316 1850.455322 
1901.411133} {curve x953 0 1.567504883 3.957641602 6.97467041 
10.8840332 17.48901367
 25.74554443 34.77923584 44.21105957 53.31280518 64.17523193 74.26617432 
 84.65118408 94.36529541 105.1884766 116.8099976 126.2409668 133.4041748 
 138.5293579 143.5074463 146.8376465

Re: [Nuke-users] Can I use 2D track for 3D Camera?

2012-09-14 Thread Todd Groves 
Thanks, Howard, that's awesome.



On Sep 14, 2012, at 9:28 AM, Howard Jones wrote:

 FWIW I've modified this today for the particle shot I'm doing and added depth 
 as well as scene scale knobs,
 so you can manually push it back/forward in Z. Also an option to auto scale 
 the geo so as you increase the scene the geo scales the same apparent size in 
 frame.
 
 Also I found an 'addLayer {rgba.beta}' line in the last one so you should 
 remove that if you dont use this version (same version name)
 
 Cheers 
 Howard
 
 From: Todd t...@nulightfx.com
 To: Nuke user discussion nuke-users@support.thefoundry.co.uk 
 Sent: Friday, 14 September 2012, 2:09
 Subject: Re: [Nuke-users] Can I use 2D track for 3D Camera?
 
 Basically I simply increased the scale until it looked right. I went by 
 nothing in particular. I probably could look into more detail next time. 
 
 Thanks everyone for your help.
 
 Howard Jones wrote:
 
 
 Out of interest did it work as Randy says. The tracker2camera is based on 1 
 unit as far as I can tell. So did it work with a straight match of units? I 
 know I wrote it but it's like bread - I don't have to know how to make it to 
 drop toast butter side down. 
 
 Haven't not used it for a long time I've just realised for a shot I'm doing 
 with particles it will give me a quick way of tracking the emitting geo in. 
 So been a useful relook at an old tool for me. 
 
 I don't think I ever sussed out object scaling properly but I might look at 
 that as well again. Though of course it'll never be a 3D tracker. 
 
 Howard
 
 On 13 Sep 2012, at 23:50, Todd Groves t...@nulightfx.com wrote:
 
 Thanks, Randy. I got it working. :)
 
 
 
 On Sep 13, 2012, at 3:11 PM, Randy Little wrote:
 
 You have to make sure you units in Nuke and Modo are the same. and when you 
 import make sure the units are set correctly
 
 Randy S. Little
 http://www.rslittle.com
  http://www.imdb.com/name/nm2325729/
 
 
 
 
 
 On Thu, Sep 13, 2012 at 2:59 PM, Todd Groves t...@nulightfx.com wrote:
  
 I found it. I just have to scale it dramatically to match the size of the 
 shots needs.
 
 
 
 
 On Sep 13, 2012, at 2:51 PM, Todd Groves wrote:
  
 How do I scale the scene? The Camera moves in my 3D program, but only 
 slightly; which means I need to scale the scene before generating the FBX.
 
  
 
 
 On Sep 13, 2012, at 2:26 PM, Marten Blumen wrote:
 
 Not sure why it doesn't work, I can see the camera moving here
 
 On 14 September 2012 08:57, Todd Groves t...@nulightfx.com wrote:

 Hey Howard,
 
 The Axis moves, but the Camera doesn't move. Will that change if I use 
 WriteGeo to generate an FBX version?

 
 
 
 On Sep 13, 2012, at 1:18 PM, Howard Jones wrote:
 
HI Todd
 
 Script below. Your track range is 953-987 correct?
 
 Anyway I put your track into the tracker2Camera gizmo
 Created camera using 'create camera' under the 'Translate solves'
 
 That was it - worked fine, might even match your image. Use the latest 
 Tracker2Camera (attached again)

 The script below is set to HD as I dont know what format you are working 
 in.
  
 Howard

 set cut_paste_input [stack 0]
 version  7.0 v1b38
 push $cut_paste_input
 Tracker3 {
  track1 {{curve x953 1192 1247.527466 1304.445923 1361.67395 1420.560303 
 1482.739014 1548.128296 1610.351685 1671.486572 1732.383667 1793.790527 
 1853.362915 1912.415894 1974.61438 2034.171753 2091.987915 2145.516113 
 2197.037842 2249.268921 2301.771729 2353.022583 2401.169312 2450.260254 
 2500.791992 2553.439941 2607.471924 2661.059082 2713.591431 2765.387695 
 2819.274414 2875.749146 2933.259277 2988.799438 3042.455322 3093.411133} 
 {curve x953 818 819.5675049 821.9576416 824.9746704 828.8840332 
 835.4890137 843.7455444 852.7792358 862.2110596 871.3128052 882.1752319 
 892.2661743 902.6511841 912.3652954 923.1884766 934.8099976 944.2409668 
 951.4041748 956.5293579 961.5074463 964.8376465 967.0097046 968.0718994 
 968.6292114 970.2266846 971.1508179 972.5056763 972.8568115 973.5623779 
 974.3269043 975.4362183 977.2075195 979.0283813 981.0758057 983.494873}}
 offset1 {0 0}
  pattern1 {-104 -54  104 54}
  search1 {-84 -77 84 77}
  track2 {1126 474}
  offset2 {0 0}
  pattern2 {-32 -32 32 32}
  search2 {-22 -22 22 22}
  track3 {1126 678}
  offset3 {0 0}
  pattern3 {-32 -32 32 32}
  search3 {-22 -22 22 22}
 track4 {922 678}
  offset4 {0 0}
  pattern4 {-32 -32 32 32}
  search4 {-22 -22 22 22}
  transform match-move
  reference_frame 953
  translate {{curve x953 0 55.52746582 112.4459229 169.6739502 
 228.5603027 290.7390137 356.1282959 418.3516846 479.4865723 540.383667 
 601.7905273 661.362915 720.4158936 782.6143799 842.1717529 899.987793 
 953.5161133 1005.037842 1057.269043 1109.771729 1161.022461 1209.169434 
 1258.260254 1308.791992 1361.439941 1415.471924 1469.059082 1521.591309 
 1573.387695 1627.274414 1683.749023 1741.259277 1796.799316 1850.455322 
 1901.411133} {curve x953 0 1.567504883 3.957641602 6.97467041 10.8840332 
 17.48901367  25.74554443

Re: [Nuke-users] Can I use 2D track for 3D Camera?

2012-09-13 Thread Howard Jones 
Send me your track and I'll send you the camera. 

Howard

On 13 Sep 2012, at 02:30, Todd Groves t...@nulightfx.com wrote:

 I thought by tracking a feature, I could paste that info into 2D track in 
 the gizmo, then create camera to generate a moving camera. But, the camera 
 doesn't move.
 When I generate a scene and axis, the axis does move. Is there some way to 
 attach the camera to the axis to make the camera move? Or am I missing a step 
 here in creating 
 a moving camera? Pressing create camera alone hasn't generated a moving 
 camera.
 
 
 
 
 On Sep 12, 2012, at 4:25 PM, Todd Groves wrote:
 
 I'm not sure I understand. I thought the gizmo was a replacement for the 
 CameraTracker.
 What's the workflow for this gizmo?
 
 
 
 On Sep 12, 2012, at 4:15 PM, Marten Blumen wrote:
 
 When you paste in the 2d track you then solve the camera. Its like
 adding a really good tracking marker
 
 On 9/13/12, Todd Groves t...@nulightfx.com wrote:
 I did that, and pasted the 2D tracker data. But the camera does not move.
 Do I still track features?
 
 
 
 
 On Sep 12, 2012, at 1:43 PM, Marten Blumen wrote:
 
 Use the 'Add User Track' btn in Tracking tab in the CameraTracking node.
 
 
 On 13 September 2012 08:13, Todd Groves t...@nulightfx.com wrote:
 In a shot I'm trying to get a Camera Track for, there is not enough
 parallax for the Cam Tracker to capture the dolly movement. Instead it
 interprets the camera movement as a pan.
 
 I believe if I can somehow use my 2D tracking information and apply it to
 the camera, I can use that inside my 3D app. Any suggestions?
 
 Thanks in advance.
 
 
 ___
 Nuke-users mailing list
 Nuke-users@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/
 http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users
 
 ___
 Nuke-users mailing list
 Nuke-users@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/
 http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users
 
 
 
 -- 
 Sent from my mobile device
 ___
 Nuke-users mailing list
 Nuke-users@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/
 http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users
 
 ___
 Nuke-users mailing list
 Nuke-users@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/
 http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users
 
 ___
 Nuke-users mailing list
 Nuke-users@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/
 http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users
___
Nuke-users mailing list
Nuke-users@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/
http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users

Re: [Nuke-users] Can I use 2D track for 3D Camera?

2012-09-13 Thread Julik Tarkhanov 

On 12 sep. 2012, at 22:13, Todd Groves wrote:

 In a shot I'm trying to get a Camera Track for, there is not enough parallax 
 for the Cam Tracker to capture the dolly movement. Instead it interprets the 
 camera movement as a pan.
 
 I believe if I can somehow use my 2D tracking information and apply it to the 
 camera, I can use that inside my 3D app. Any suggestions?


You could use Tracksperanto and convert the Tracker nodes in your Nuke script 
(or the features generated by the CameraTracker node) into a set of Maya or 
Softimage
locators floating on an image plane, and then use an aim constraint on the 
camera to turn the camera towards the locators. However, you could also do that 
in Nuke with some
expressions I think.
-- 
Julik Tarkhanov | HecticElectric | Keizersgracht 736 1017 EX
Amsterdam | The Netherlands | tel. +31 20 330 8250
cel. +31 61 145 06 36 | http://hecticelectric.nl

___
Nuke-users mailing list
Nuke-users@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/
http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users

Re: [Nuke-users] Can I use 2D track for 3D Camera?

2012-09-13 Thread Howard Jones 
Also here is a new version that allows for scene scale (sort of)


 
Howard




 From: Howard Jones mrhowardjo...@yahoo.com
To: Nuke user discussion nuke-users@support.thefoundry.co.uk 
Sent: Thursday, 13 September 2012, 10:02
Subject: Re: [Nuke-users] Can I use 2D track for 3D Camera?
 

Here's a script I just tested. The mistake I said earlier is the geo needs to 
be placed at z -1  not 0 as that is where the camera is
The camera move starts about frame 180. The camera was made where indicated on 
the attached screen grab  and the tracker copied to where indicated.

Howard


set cut_paste_input [stack 0]
version 6.3 v8
ColorBars {
 inputs 0
 name ColorBars1
 selected true
 xpos
 -393
 ypos 46
}
set N2350dcc0 [stack 0]
Tracker3 {
 track1 {{curve i x168 565.0580444 565.0506592 565.0808105 565.0734863 
565.090332 565.0900269 565.0386963 565.0371704 565.0344849 565.0802612 
565.0743408 565.02771 565.0435181 565.0272827 565.0499878 565.0512695 
565.041687 565.0303345 565.0404663 565.0328369 565.0270386 565.0550537 
565.0609741 565.0543823 564.9695435 565.0925903 565.100708 565.1529541 
565.1568604 565.2304688 565.2637939 565.5274658 566.0942993 567.1130371 
568.5047607 570.1556396 572 574.0427246 576.4594727 579.5081787 582.8543701 
586.4736328 590.6512451 595.4264526 600.788147 606.6361694 613.3390503 
620.9207153 628.4902344 636.2153931 643.87146 651.5625 659.1858521 666.7214966 
674.1802368 681.5661621 689.1931763 696.713623 704.0188599 711.1591187 
717.930603 724.4248657 730.7055664 736.8729248 742.8016357 748.3226929 
753.6640015 758.7963257 763.5657959 768.1853638 772.6127319 776.8475342 
780.8762207 784.8641968}
 {curve i x168 914.9620972 914.9147339 914.9519653 915.0713501 915.1292114 
915.1333008 915.0280151 914.9485474 915.0281372 915.1885986 915.2176514 
915.0997314 914.9534912 915.0742798 915.1473999 915.1834717 915.1062012 
914.949585 915.0661011 915.0748901 915.1035156 915.1271973 915.102417 
914.973999 914.9142456 914.9026489 914.8991089 914.8400879 914.8340454 
914.8428955 914.9118042 915.0114136 915.0579834 915.0649414 915.3963013 
915.7054443 916 916.4089355 916.6481934 916.9378662 917.2780762 917.6220703 
918.2166138 919.0627441 919.9505615 921.2800293 923.1519775 924.7025757 
926.5269165 928.3306885 930.2348633 932.3450317 934.6914062 937.2457886 
940.0419312 943.072876 946.4127808 950.2473755 954.3674316 959.178894 
964.5707397 969.9567871 975.8885498 982.1394653 988.5229492 995.1955566 
1001.587158 1008.258301 1015.108521 1021.897705 1028.883911 1035.780273 
1041.881104 1047.743774}}
 offset1 {0 0}
 pattern1 {-30 -30 30 30}
 search1
 {-21 -21 21 21}
 track2 {1055 445}
 offset2 {0 0}
 pattern2 {-30 -30 30 30}
 search2 {-21 -21 21 21}
 track3 {1055 635}
 offset3 {0 0}
 pattern3 {-30 -30 30 30}
 search3 {-21 -21 21 21}
 track4 {865 635}
 offset4 {0 0}
 pattern4 {-30 -30 30 30}
 search4 {-21 -21 21 21}
 translate {{curve i x168 0 -0.007385253906 0.02276611328 0.01544189453 
0.03228759766 0.03198242188 -0.01934814453 -0.02087402344 -0.02355957031 
0.02221679688 0.01629638672 -0.03033447266 -0.01452636719 -0.03076171875 
-0.008056640625 -0.006774902344 -0.01635742188 -0.02770996094 -0.017578125 
-0.02520751953 -0.03100585938 -0.002990722656 0.0029296875 -0.003662109375 
-0.08850097656 0.03454589844 0.04266357422 0.09490966797 0.09881591797 
0.1724243164 0.2057495117 0.4694213867 1.036254883 2.054992676 3.446716309 
5.097595215 6.941955566 8.984680176 11.40142822 14.45013428 17.79632568
 21.41558838 25.59320068 30.3684082 35.73010254 41.578125 48.28100586 
55.8626709 63.43218994 71.15734863 78.81341553 86.50445557 94.12780762 
101.6634521 109.1221924 116.5081177 124.1351318 131.6555786 138.9608154 
146.1010742 152.8725586 159.3668213 165.647522 171.8148804 177.7435913 
183.2646484 188.605957 193.7382812 198.5077515 203.1273193 207.5546875 
211.7894897 215.8181763 219.8061523} {curve i x168 0 -0.04736328125 
-0.01013183594 0.1092529297 0.1671142578 0.1712036133 0.06591796875 
-0.01354980469 0.06604003906 0.2265014648 0.241992 0.1376342773 
-0.008605957031 0.1121826172 0.1853027344 0.2213745117 0.1441040039 
-0.01251220703 0.1040039062 0.1127929688 0.141418457 0.1651000977 0.1403198242 
0.01190185547 -0.0478515625 -0.05944824219 -0.06298828125 -0.1220092773 
-0.1280517578 -0.1192016602 -0.05029296875 0.04931640625 0.09588623047 
0.1028442383 0.4342041016 0.743347168 1.037902832 1.446838379 1.686096191 
1.975769043 2.315979004 2.659973145
 3.254516602 4.100646973 4.988464355 6.317932129 8.189880371 9.740478516 
11.56481934 13.36859131 15.27276611 17.38293457 19.72930908 22.28369141 
25.07983398 28.11077881 31.45068359 35.28527832 39.40533447 44.21679688 
49.60864258 54.99468994 60.92645264 67.17736816 73.56085205 80.23345947 
86.62506104 93.29620361 100.1464233 106.9356079 113.921814 120.8181763 
126.9190063 132.7816772}}
 center {{curve i x168 565.0580444 565.0580444 565.0580444 565.0580444 
565.0580444 565.0580444 565.0580444 565.0580444 565.0580444

Re: [Nuke-users] Can I use 2D track for 3D Camera?

2012-09-13 Thread Howard Jones 
Oops wrong internal name - reattached - also with this version geo is 
positioned at z=0

 
Howard




 From: Howard Jones mrhowardjo...@yahoo.com
To: Nuke user discussion nuke-users@support.thefoundry.co.uk 
Sent: Thursday, 13 September 2012, 10:30
Subject: Re: [Nuke-users] Can I use 2D track for 3D Camera?
 

Also here is a new version that allows for scene scale (sort of)



 
Howard




 From: Howard Jones mrhowardjo...@yahoo.com
To: Nuke user discussion nuke-users@support.thefoundry.co.uk 
Sent: Thursday, 13 September 2012, 10:02
Subject: Re: [Nuke-users] Can I use 2D track for 3D Camera?
 

Here's a script I just tested. The mistake I said earlier is the geo needs to 
be placed at z -1  not 0 as that is where the camera is
The camera move starts about frame 180. The camera was made where indicated 
on the attached screen grab  and the tracker copied to where indicated.

Howard


set cut_paste_input [stack 0]
version 6.3 v8
ColorBars {
 inputs 0
 name ColorBars1
 selected true
 xpos
 -393
 ypos 46
}
set N2350dcc0 [stack 0]
Tracker3 {
 track1 {{curve i x168 565.0580444 565.0506592 565.0808105 565.0734863 
565.090332 565.0900269 565.0386963 565.0371704 565.0344849 565.0802612 
565.0743408 565.02771 565.0435181 565.0272827 565.0499878 565.0512695 
565.041687 565.0303345 565.0404663 565.0328369 565.0270386 565.0550537 
565.0609741 565.0543823 564.9695435 565.0925903 565.100708 565.1529541 
565.1568604 565.2304688 565.2637939 565.5274658 566.0942993 567.1130371 
568.5047607 570.1556396 572 574.0427246 576.4594727 579.5081787 582.8543701 
586.4736328 590.6512451 595.4264526 600.788147 606.6361694 613.3390503 
620.9207153 628.4902344 636.2153931 643.87146 651.5625 659.1858521 
666.7214966 674.1802368 681.5661621 689.1931763 696.713623 704.0188599 
711.1591187 717.930603 724.4248657 730.7055664 736.8729248 742.8016357 
748.3226929 753.6640015 758.7963257 763.5657959 768.1853638 772.6127319 
776.8475342 780.8762207 784.8641968}
 {curve i x168 914.9620972 914.9147339 914.9519653 915.0713501 915.1292114 
915.1333008 915.0280151 914.9485474 915.0281372 915.1885986 915.2176514 
915.0997314 914.9534912 915.0742798 915.1473999 915.1834717 915.1062012 
914.949585 915.0661011 915.0748901 915.1035156 915.1271973 915.102417 
914.973999 914.9142456 914.9026489 914.8991089 914.8400879 914.8340454 
914.8428955 914.9118042 915.0114136 915.0579834 915.0649414 915.3963013 
915.7054443 916 916.4089355 916.6481934 916.9378662 917.2780762 917.6220703 
918.2166138 919.0627441 919.9505615 921.2800293 923.1519775 924.7025757 
926.5269165 928.3306885 930.2348633 932.3450317 934.6914062 937.2457886 
940.0419312 943.072876 946.4127808 950.2473755 954.3674316 959.178894 
964.5707397 969.9567871 975.8885498 982.1394653 988.5229492 995.1955566 
1001.587158 1008.258301 1015.108521 1021.897705 1028.883911 1035.780273 
1041.881104 1047.743774}}
 offset1 {0 0}
 pattern1 {-30 -30 30 30}
 search1
 {-21 -21 21 21}
 track2 {1055 445}
 offset2 {0 0}
 pattern2 {-30 -30 30 30}
 search2 {-21 -21 21 21}
 track3 {1055 635}
 offset3 {0 0}
 pattern3 {-30 -30 30 30}
 search3 {-21 -21 21 21}
 track4 {865 635}
 offset4 {0 0}
 pattern4 {-30 -30 30 30}
 search4 {-21 -21 21 21}
 translate {{curve i x168 0 -0.007385253906 0.02276611328 0.01544189453 
0.03228759766 0.03198242188 -0.01934814453 -0.02087402344 -0.02355957031 
0.02221679688 0.01629638672 -0.03033447266 -0.01452636719 -0.03076171875 
-0.008056640625 -0.006774902344 -0.01635742188 -0.02770996094 -0.017578125 
-0.02520751953 -0.03100585938 -0.002990722656 0.0029296875 -0.003662109375 
-0.08850097656 0.03454589844 0.04266357422 0.09490966797 0.09881591797 
0.1724243164 0.2057495117 0.4694213867 1.036254883 2.054992676 3.446716309 
5.097595215 6.941955566 8.984680176 11.40142822 14.45013428 17.79632568
 21.41558838 25.59320068 30.3684082 35.73010254 41.578125 48.28100586 
55.8626709 63.43218994 71.15734863 78.81341553 86.50445557 94.12780762 
101.6634521 109.1221924 116.5081177 124.1351318 131.6555786 138.9608154 
146.1010742 152.8725586 159.3668213 165.647522 171.8148804 177.7435913 
183.2646484 188.605957 193.7382812 198.5077515 203.1273193 207.5546875 
211.7894897 215.8181763 219.8061523} {curve i x168 0 -0.04736328125 
-0.01013183594 0.1092529297 0.1671142578 0.1712036133 0.06591796875 
-0.01354980469 0.06604003906 0.2265014648 0.241992 0.1376342773 
-0.008605957031 0.1121826172 0.1853027344 0.2213745117 0.1441040039 
-0.01251220703 0.1040039062 0.1127929688 0.141418457 0.1651000977 0.1403198242 
0.01190185547 -0.0478515625 -0.05944824219 -0.06298828125 -0.1220092773 
-0.1280517578 -0.1192016602 -0.05029296875 0.04931640625 0.09588623047 
0.1028442383 0.4342041016 0.743347168 1.037902832 1.446838379 1.686096191 
1.975769043 2.315979004 2.659973145
 3.254516602 4.100646973 4.988464355 6.317932129 8.189880371 9.740478516 
11.56481934 13.36859131 15.27276611 17.38293457 19.72930908 22.28369141 
25.07983398 28.11077881 31.45068359

Re: [Nuke-users] Can I use 2D track for 3D Camera?

2012-09-13 Thread Todd Groves 
Hi Howard,

Here's my 2D Tracker. Plus, can you tell me how you applied it? Did you use the 
gizmo?  Thanks. 

set cut_paste_input [stack 0]
version 6.3 v4
push $cut_paste_input
Tracker3 {
 track1 {{curve x953 1192 1247.527466 1304.445923 1361.67395 1420.560303 
1482.739014 1548.128296 1610.351685 1671.486572 1732.383667 1793.790527 
1853.362915 1912.415894 1974.61438 2034.171753 2091.987915 2145.516113 
2197.037842 2249.268921 2301.771729 2353.022583 2401.169312 2450.260254 
2500.791992 2553.439941 2607.471924 2661.059082 2713.591431 2765.387695 
2819.274414 2875.749146 2933.259277 2988.799438 3042.455322 3093.411133} {curve 
x953 818 819.5675049 821.9576416 824.9746704 828.8840332 835.4890137 
843.7455444 852.7792358 862.2110596 871.3128052 882.1752319 892.2661743 
902.6511841 912.3652954 923.1884766 934.8099976 944.2409668 951.4041748 
956.5293579 961.5074463 964.8376465 967.0097046 968.0718994 968.6292114 
970.2266846 971.1508179 972.5056763 972.8568115 973.5623779 974.3269043 
975.4362183 977.2075195 979.0283813 981.0758057 983.494873}}
 offset1 {0 0}
 pattern1 {-104 -54 104 54}
 search1 {-84 -77 84 77}
 track2 {1126 474}
 offset2 {0 0}
 pattern2 {-32 -32 32 32}
 search2 {-22 -22 22 22}
 track3 {1126 678}
 offset3 {0 0}
 pattern3 {-32 -32 32 32}
 search3 {-22 -22 22 22}
 track4 {922 678}
 offset4 {0 0}
 pattern4 {-32 -32 32 32}
 search4 {-22 -22 22 22}
 transform match-move
 reference_frame 953
 translate {{curve x953 0 55.52746582 112.4459229 169.6739502 228.5603027 
290.7390137 356.1282959 418.3516846 479.4865723 540.383667 601.7905273 
661.362915 720.4158936 782.6143799 842.1717529 899.987793 953.5161133 
1005.037842 1057.269043 1109.771729 1161.022461 1209.169434 1258.260254 
1308.791992 1361.439941 1415.471924 1469.059082 1521.591309 1573.387695 
1627.274414 1683.749023 1741.259277 1796.799316 1850.455322 1901.411133} {curve 
x953 0 1.567504883 3.957641602 6.97467041 10.8840332 17.48901367 25.74554443 
34.77923584 44.21105957 53.31280518 64.17523193 74.26617432 84.65118408 
94.36529541 105.1884766 116.8099976 126.2409668 133.4041748 138.5293579 
143.5074463 146.8376465 149.0097046 150.0718994 150.6292114 152.2266846 
153.1508179 154.5056763 154.8568115 155.5623779 156.3269043 157.4362183 
159.2075195 161.0283813 163.0758057 165.494873}}
 center {{curve x953 1192 1192 1192 1192 1192 1192 1192 1192 1192 1192 1192 
1192 1192 1192 1192 1192 1192 1192 1192 1192 1192 1192 1192 1192 1192 1192 1192 
1192 1192 1192 1192 1192 1192 1192 1192} {curve x953 818 818 818 818 818 818 
818 818 818 818 818 818 818 818 818 818 818 818 818 818 818 818 818 818 818 818 
818 818 818 818 818 818 818 818 818}}
 name Tracker1
 selected true
 xpos 361
 ypos -87
}












On Sep 13, 2012, at 12:14 AM, Howard Jones wrote:

 Send me your track and I'll send you the camera. 
 
 Howard
 
 On 13 Sep 2012, at 02:30, Todd Groves t...@nulightfx.com wrote:
 
 I thought by tracking a feature, I could paste that info into 2D track in 
 the gizmo, then create camera to generate a moving camera. But, the camera 
 doesn't move.
 When I generate a scene and axis, the axis does move. Is there some way to 
 attach the camera to the axis to make the camera move? Or am I missing a 
 step here in creating 
 a moving camera? Pressing create camera alone hasn't generated a moving 
 camera.
 
 
 
 
 On Sep 12, 2012, at 4:25 PM, Todd Groves wrote:
 
 I'm not sure I understand. I thought the gizmo was a replacement for the 
 CameraTracker.
 What's the workflow for this gizmo?
 
 
 
 On Sep 12, 2012, at 4:15 PM, Marten Blumen wrote:
 
 When you paste in the 2d track you then solve the camera. Its like
 adding a really good tracking marker
 
 On 9/13/12, Todd Groves t...@nulightfx.com wrote:
 I did that, and pasted the 2D tracker data. But the camera does not move.
 Do I still track features?
 
 
 
 
 On Sep 12, 2012, at 1:43 PM, Marten Blumen wrote:
 
 Use the 'Add User Track' btn in Tracking tab in the CameraTracking node.
 
 
 On 13 September 2012 08:13, Todd Groves t...@nulightfx.com wrote:
 In a shot I'm trying to get a Camera Track for, there is not enough
 parallax for the Cam Tracker to capture the dolly movement. Instead it
 interprets the camera movement as a pan.
 
 I believe if I can somehow use my 2D tracking information and apply it to
 the camera, I can use that inside my 3D app. Any suggestions?
 
 Thanks in advance.
 
 
 ___
 Nuke-users mailing list
 Nuke-users@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/
 http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users
 
 ___
 Nuke-users mailing list
 Nuke-users@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/
 http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users
 
 
 
 -- 
 Sent from my mobile device
 ___
 Nuke-users mailing list
 Nuke-users@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/

Re: [Nuke-users] Can I use 2D track for 3D Camera?

2012-09-13 Thread Howard Jones 
HI Todd

Script below. Your track range is 953-987 correct?

Anyway I put your track into the tracker2Camera gizmo
Created camera using 'create camera' under the 'Translate solves'

That was it - worked fine, might even match your image. Use the latest 
Tracker2Camera (attached again)

The script below is set to HD as I dont know what format you are working in.

 
Howard

set cut_paste_input [stack 0]
version 7.0 v1b38
push $cut_paste_input
Tracker3 {
 track1 {{curve x953 1192 1247.527466 1304.445923 1361.67395 1420.560303 
1482.739014 1548.128296 1610.351685 1671.486572 1732.383667 1793.790527 
1853.362915 1912.415894 1974.61438 2034.171753 2091.987915 2145.516113 
2197.037842 2249.268921 2301.771729 2353.022583 2401.169312 2450.260254 
2500.791992 2553.439941 2607.471924 2661.059082 2713.591431 2765.387695 
2819.274414 2875.749146 2933.259277 2988.799438 3042.455322 3093.411133} {curve 
x953 818 819.5675049 821.9576416 824.9746704 828.8840332 835.4890137 
843.7455444 852.7792358 862.2110596 871.3128052 882.1752319 892.2661743 
902.6511841 912.3652954 923.1884766 934.8099976 944.2409668 951.4041748 
956.5293579 961.5074463 964.8376465 967.0097046 968.0718994 968.6292114 
970.2266846 971.1508179 972.5056763 972.8568115 973.5623779 974.3269043 
975.4362183 977.2075195 979.0283813 981.0758057 983.494873}}
 offset1 {0 0}
 pattern1 {-104 -54 104 54}
 search1 {-84 -77 84 77}
 track2 {1126 474}
 offset2 {0 0}
 pattern2 {-32 -32 32 32}
 search2 {-22 -22 22 22}
 track3 {1126 678}
 offset3 {0 0}
 pattern3 {-32 -32 32 32}
 search3 {-22 -22 22 22}
 track4 {922 678}
 offset4 {0 0}
 pattern4 {-32 -32 32 32}
 search4 {-22 -22 22 22}
 transform match-move
 reference_frame 953
 translate {{curve x953 0 55.52746582 112.4459229 169.6739502 228.5603027 
290.7390137 356.1282959 418.3516846 479.4865723 540.383667 601.7905273 
661.362915 720.4158936 782.6143799 842.1717529 899.987793 953.5161133 
1005.037842 1057.269043 1109.771729 1161.022461 1209.169434 1258.260254 
1308.791992 1361.439941 1415.471924 1469.059082 1521.591309 1573.387695 
1627.274414 1683.749023 1741.259277 1796.799316 1850.455322 1901.411133} {curve 
x953 0 1.567504883 3.957641602 6.97467041 10.8840332 17.48901367 25.74554443 
34.77923584 44.21105957 53.31280518 64.17523193 74.26617432 84.65118408 
94.36529541 105.1884766 116.8099976 126.2409668 133.4041748 138.5293579 
143.5074463 146.8376465 149.0097046 150.0718994 150.6292114 152.2266846 
153.1508179 154.5056763 154.8568115 155.5623779 156.3269043 157.4362183 
159.2075195 161.0283813 163.0758057 165.494873}}
 center {{curve x953 1192 1192 1192 1192 1192 1192 1192 1192 1192 1192 1192 
1192 1192 1192 1192 1192 1192 1192 1192 1192 1192 1192 1192 1192 1192 1192 1192 
1192 1192 1192 1192 1192 1192 1192 1192} {curve x953 818 818 818 818 818 818 
818 818 818 818 818 818 818 818 818 818 818 818 818 818 818 818 818 818 818 818 
818 818 818 818 818 818 818 818 818}}
 name Tracker1
 selected true
 xpos -271
 ypos 130
}
CheckerBoard2 {
 inputs 0
 name CheckerBoard1
 selected true
 xpos -86
 ypos 131
}
Sphere {
 radius 0.01
 name Sphere1
 selected true
 xpos -86
 ypos 227
}
Camera2 {
 inputs 0
 translate {{-Tracker2Camera.solvedTranslate} {-Tracker2Camera.solvedTranslate} 
{-Tracker2Camera.solvedTranslate}}
 focal {{Tracker2Camera.focalLengthCalc}}
 haperture {{Tracker2Camera.apertureCalc.x}}
 vaperture {{Tracker2Camera.apertureCalc.y}}
 name Camera1
 label translate
 selected true
 xpos -255
 ypos 247
}
Scene {
 inputs 2
 name Scene1
 selected true
 xpos -76
 ypos 290
}
tracker2Camera2 {
 inputs 0
 name Tracker2Camera
 note_font Arial
 selected true
 xpos -270
 ypos 179
 format 0
 apertureCalc {24.576 {apertureCalc.x*height/width}}
 fovCalc {{degrees(2*atan(apertureCalc/(2*focalLengthCalc)))} 
{degrees(2*atan(apertureCalc/(2*focalLengthCalc)))}}
 apertureFocalRatio {{apertureCalc.x/focalLengthCalc.main}}
 Trax01 {{curve x953 1192 1247.527466 1304.445923 1361.67395 1420.560303 
1482.739014 1548.128296 1610.351685 1671.486572 1732.383667 1793.790527 
1853.362915 1912.415894 1974.61438 2034.171753 2091.987915 2145.516113 
2197.037842 2249.268921 2301.771729 2353.022583 2401.169312 2450.260254 
2500.791992 2553.439941 2607.471924 2661.059082 2713.591431 2765.387695 
2819.274414 2875.749146 2933.259277 2988.799438 3042.455322 3093.411133} {curve 
x953 818 819.5675049 821.9576416 824.9746704 828.8840332 835.4890137 
843.7455444 852.7792358 862.2110596 871.3128052 882.1752319 892.2661743 
902.6511841 912.3652954 923.1884766 934.8099976 944.2409668 951.4041748 
956.5293579 961.5074463 964.8376465 967.0097046 968.0718994 968.6292114 
970.2266846 971.1508179 972.5056763 972.8568115 973.5623779 974.3269043 
975.4362183 977.2075195 979.0283813 981.0758057 983.494873}}
 solved3D {{-(Trax01.y/height-0.5)*fovCalc.y} {(Trax01.x/width-0.5)*fovCalc.x} 
0}
 solvedTranslate {{(Trax01.x-width/2)/width*apertureFocalRatio*scaleScene} 
{(Trax01.y-height/2)/width*apertureFocalRatio*scaleScene} {-scaleScene}}
}

tracker2Camera2.gizmo

Re: [Nuke-users] Can I use 2D track for 3D Camera?

2012-09-13 Thread Todd Groves 
Hey Howard,

The Axis moves, but the Camera doesn't move. Will that change if I use WriteGeo 
to generate an FBX version?



On Sep 13, 2012, at 1:18 PM, Howard Jones wrote:

 HI Todd
 
 Script below. Your track range is 953-987 correct?
 
 Anyway I put your track into the tracker2Camera gizmo
 Created camera using 'create camera' under the 'Translate solves'
 
 That was it - worked fine, might even match your image. Use the latest 
 Tracker2Camera (attached again)
 
 The script below is set to HD as I dont know what format you are working in.
  
 Howard
 
 set cut_paste_input [stack 0]
 version 7.0 v1b38
 push $cut_paste_input
 Tracker3 {
  track1 {{curve x953 1192 1247.527466 1304.445923 1361.67395 1420.560303 
 1482.739014 1548.128296 1610.351685 1671.486572 1732.383667 1793.790527 
 1853.362915 1912.415894 1974.61438 2034.171753 2091.987915 2145.516113 
 2197.037842 2249.268921 2301.771729 2353.022583 2401.169312 2450.260254 
 2500.791992 2553.439941 2607.471924 2661.059082 2713.591431 2765.387695 
 2819.274414 2875.749146 2933.259277 2988.799438 3042.455322 3093.411133} 
 {curve x953 818 819.5675049 821.9576416 824.9746704 828.8840332 835.4890137 
 843.7455444 852.7792358 862.2110596 871.3128052 882.1752319 892.2661743 
 902.6511841 912.3652954 923.1884766 934.8099976 944.2409668 951.4041748 
 956.5293579 961.5074463 964.8376465 967.0097046 968.0718994 968.6292114 
 970.2266846 971.1508179 972.5056763 972.8568115 973.5623779 974.3269043 
 975.4362183 977.2075195 979.0283813 981.0758057 983.494873}}
  offset1 {0 0}
  pattern1 {-104 -54 104 54}
  search1 {-84 -77 84 77}
  track2 {1126 474}
  offset2 {0 0}
  pattern2 {-32 -32 32 32}
  search2 {-22 -22 22 22}
  track3 {1126 678}
  offset3 {0 0}
  pattern3 {-32 -32 32 32}
  search3 {-22 -22 22 22}
  track4 {922 678}
  offset4 {0 0}
  pattern4 {-32 -32 32 32}
  search4 {-22 -22 22 22}
  transform match-move
  reference_frame 953
  translate {{curve x953 0 55.52746582 112.4459229 169.6739502 228.5603027 
 290.7390137 356.1282959 418.3516846 479.4865723 540.383667 601.7905273 
 661.362915 720.4158936 782.6143799 842.1717529 899.987793 953.5161133 
 1005.037842 1057.269043 1109.771729 1161.022461 1209.169434 1258.260254 
 1308.791992 1361.439941 1415.471924 1469.059082 1521.591309 1573.387695 
 1627.274414 1683.749023 1741.259277 1796.799316 1850.455322 1901.411133} 
 {curve x953 0 1.567504883 3.957641602 6.97467041 10.8840332 17.48901367 
 25.74554443 34.77923584 44.21105957 53.31280518 64.17523193 74.26617432 
 84.65118408 94.36529541 105.1884766 116.8099976 126.2409668 133.4041748 
 138.5293579 143.5074463 146.8376465 149.0097046 150.0718994 150.6292114 
 152.2266846 153.1508179 154.5056763 154.8568115 155.5623779 156.3269043 
 157.4362183 159.2075195 161.0283813 163.0758057 165.494873}}
  center {{curve x953 1192 1192 1192 1192 1192 1192 1192 1192 1192 1192 1192 
 1192 1192 1192 1192 1192 1192 1192 1192 1192 1192 1192 1192 1192 1192 1192 
 1192 1192 1192 1192 1192 1192 1192 1192 1192} {curve x953 818 818 818 818 818 
 818 818 818 818 818 818 818 818 818 818 818 818 818 818 818 818 818 818 818 
 818 818 818 818 818 818 818 818 818 818 818}}
  name Tracker1
  selected true
  xpos -271
  ypos 130
 }
 CheckerBoard2 {
  inputs 0
  name CheckerBoard1
  selected true
  xpos -86
  ypos 131
 }
 Sphere {
  radius 0.01
  name Sphere1
  selected true
  xpos -86
  ypos 227
 }
 Camera2 {
  inputs 0
  translate {{-Tracker2Camera.solvedTranslate} 
 {-Tracker2Camera.solvedTranslate} {-Tracker2Camera.solvedTranslate}}
  focal {{Tracker2Camera.focalLengthCalc}}
  haperture {{Tracker2Camera.apertureCalc.x}}
  vaperture {{Tracker2Camera.apertureCalc.y}}
  name Camera1
  label translate
  selected true
  xpos -255
  ypos 247
 }
 Scene {
  inputs 2
  name Scene1
  selected true
  xpos -76
  ypos 290
 }
 tracker2Camera2 {
  inputs 0
  name Tracker2Camera
  note_font Arial
  selected true
  xpos -270
  ypos 179
  format 0
  apertureCalc {24.576 {apertureCalc.x*height/width}}
  fovCalc {{degrees(2*atan(apertureCalc/(2*focalLengthCalc)))} 
 {degrees(2*atan(apertureCalc/(2*focalLengthCalc)))}}
  apertureFocalRatio {{apertureCalc.x/focalLengthCalc.main}}
  Trax01 {{curve x953 1192 1247.527466 1304.445923 1361.67395 1420.560303 
 1482.739014 1548.128296 1610.351685 1671.486572 1732.383667 1793.790527 
 1853.362915 1912.415894 1974.61438 2034.171753 2091.987915 2145.516113 
 2197.037842 2249.268921 2301.771729 2353.022583 2401.169312 2450.260254 
 2500.791992 2553.439941 2607.471924 2661.059082 2713.591431 2765.387695 
 2819.274414 2875.749146 2933.259277 2988.799438 3042.455322 3093.411133} 
 {curve x953 818 819.5675049 821.9576416 824.9746704 828.8840332 835.4890137 
 843.7455444 852.7792358 862.2110596 871.3128052 882.1752319 892.2661743 
 902.6511841 912.3652954 923.1884766 934.8099976 944.2409668 951.4041748 
 956.5293579 961.5074463 964.8376465 967.0097046 968.0718994 968.6292114 
 970.2266846 971.1508179 972.5056763 972.8568115 973.5623779 974.3269043 
 975.4362183 977.2075195

Re: [Nuke-users] Can I use 2D track for 3D Camera?

2012-09-13 Thread Marten Blumen 
Not sure why it doesn't work, I can see the camera moving here

On 14 September 2012 08:57, Todd Groves t...@nulightfx.com wrote:

 Hey Howard,

 The Axis moves, but the Camera doesn't move. Will that change if I use
 WriteGeo to generate an FBX version?



 On Sep 13, 2012, at 1:18 PM, Howard Jones wrote:

 HI Todd

 Script below. Your track range is 953-987 correct?

 Anyway I put your track into the tracker2Camera gizmo
 Created camera using 'create camera' under the 'Translate solves'

 That was it - worked fine, might even match your image. Use the latest
 Tracker2Camera (attached again)

 The script below is set to HD as I dont know what format you are working
 in.

 Howard

 set cut_paste_input [stack 0]
 version 7.0 v1b38
 push $cut_paste_input
 Tracker3 {
  track1 {{curve x953 1192 1247.527466 1304.445923 1361.67395 1420.560303
 1482.739014 1548.128296 1610.351685 1671.486572 1732.383667 1793.790527
 1853.362915 1912.415894 1974.61438 2034.171753 2091.987915 2145.516113
 2197.037842 2249.268921 2301.771729 2353.022583 2401.169312 2450.260254
 2500.791992 2553.439941 2607.471924 2661.059082 2713.591431 2765.387695
 2819.274414 2875.749146 2933.259277 2988.799438 3042.455322 3093.411133}
 {curve x953 818 819.5675049 821.9576416 824.9746704 828.8840332 835.4890137
 843.7455444 852.7792358 862.2110596 871.3128052 882.1752319 892.2661743
 902.6511841 912.3652954 923.1884766 934.8099976 944.2409668 951.4041748
 956.5293579 961.5074463 964.8376465 967.0097046 968.0718994 968.6292114
 970.2266846 971.1508179 972.5056763 972.8568115 973.5623779 974.3269043
 975.4362183 977.2075195 979.0283813 981.0758057 983.494873}}
  offset1 {0 0}
  pattern1 {-104 -54 104 54}
  search1 {-84 -77 84 77}
  track2 {1126 474}
  offset2 {0 0}
  pattern2 {-32 -32 32 32}
  search2 {-22 -22 22 22}
  track3 {1126 678}
  offset3 {0 0}
  pattern3 {-32 -32 32 32}
  search3 {-22 -22 22 22}
  track4 {922 678}
  offset4 {0 0}
  pattern4 {-32 -32 32 32}
  search4 {-22 -22 22 22}
  transform match-move
  reference_frame 953
  translate {{curve x953 0 55.52746582 112.4459229 169.6739502 228.5603027
 290.7390137 356.1282959 418.3516846 479.4865723 540.383667 601.7905273
 661.362915 720.4158936 782.6143799 842.1717529 899.987793 953.5161133
 1005.037842 1057.269043 1109.771729 1161.022461 1209.169434 1258.260254
 1308.791992 1361.439941 1415.471924 1469.059082 1521.591309 1573.387695
 1627.274414 1683.749023 1741.259277 1796.799316 1850.455322 1901.411133}
 {curve x953 0 1.567504883 3.957641602 6.97467041 10.8840332 17.48901367
 25.74554443 34.77923584 44.21105957 53.31280518 64.17523193 74.26617432
 84.65118408 94.36529541 105.1884766 116.8099976 126.2409668 133.4041748
 138.5293579 143.5074463 146.8376465 149.0097046 150.0718994 150.6292114
 152.2266846 153.1508179 154.5056763 154.8568115 155.5623779 156.3269043
 157.4362183 159.2075195 161.0283813 163.0758057 165.494873}}
  center {{curve x953 1192 1192 1192 1192 1192 1192 1192 1192 1192 1192
 1192 1192 1192 1192 1192 1192 1192 1192 1192 1192 1192 1192 1192 1192 1192
 1192 1192 1192 1192 1192 1192 1192 1192 1192 1192} {curve x953 818 818 818
 818 818 818 818 818 818 818 818 818 818 818 818 818 818 818 818 818 818 818
 818 818 818 818 818 818 818 818 818 818 818 818 818}}
  name Tracker1
  selected true
  xpos -271
  ypos 130
 }
 CheckerBoard2 {
  inputs 0
  name CheckerBoard1
  selected true
  xpos -86
  ypos 131
 }
 Sphere {
  radius 0.01
  name Sphere1
  selected true
  xpos -86
  ypos 227
 }
 Camera2 {
  inputs 0
  translate {{-Tracker2Camera.solvedTranslate}
 {-Tracker2Camera.solvedTranslate} {-Tracker2Camera.solvedTranslate}}
  focal {{Tracker2Camera.focalLengthCalc}}
  haperture {{Tracker2Camera.apertureCalc.x}}
  vaperture {{Tracker2Camera.apertureCalc.y}}
  name Camera1
  label translate
  selected true
  xpos -255
  ypos 247
 }
 Scene {
  inputs 2
  name Scene1
  selected true
  xpos -76
  ypos 290
 }
 tracker2Camera2 {
  inputs 0
  name Tracker2Camera
  note_font Arial
  selected true
  xpos -270
  ypos 179
  format 0
  apertureCalc {24.576 {apertureCalc.x*height/width}}
  fovCalc {{degrees(2*atan(apertureCalc/(2*focalLengthCalc)))}
 {degrees(2*atan(apertureCalc/(2*focalLengthCalc)))}}
  apertureFocalRatio {{apertureCalc.x/focalLengthCalc.main}}
  Trax01 {{curve x953 1192 1247.527466 1304.445923 1361.67395 1420.560303
 1482.739014 1548.128296 1610.351685 1671.486572 1732.383667 1793.790527
 1853.362915 1912.415894 1974.61438 2034.171753 2091.987915 2145.516113
 2197.037842 2249.268921 2301.771729 2353.022583 2401.169312 2450.260254
 2500.791992 2553.439941 2607.471924 2661.059082 2713.591431 2765.387695
 2819.274414 2875.749146 2933.259277 2988.799438 3042.455322 3093.411133}
 {curve x953 818 819.5675049 821.9576416 824.9746704 828.8840332 835.4890137
 843.7455444 852.7792358 862.2110596 871.3128052 882.1752319 892.2661743
 902.6511841 912.3652954 923.1884766 934.8099976 944.2409668 951.4041748
 956.5293579 961.5074463 964.8376465 967.0097046 968.0718994 968.6292114

Re: [Nuke-users] Can I use 2D track for 3D Camera?

2012-09-13 Thread Todd Groves 
How do I scale the scene? The Camera moves in my 3D program, but only slightly; 
which means I need to scale the scene before generating the FBX.



On Sep 13, 2012, at 2:26 PM, Marten Blumen wrote:

 Not sure why it doesn't work, I can see the camera moving here
 
 On 14 September 2012 08:57, Todd Groves t...@nulightfx.com wrote:
 Hey Howard,
 
 The Axis moves, but the Camera doesn't move. Will that change if I use 
 WriteGeo to generate an FBX version?
 
 
 
 On Sep 13, 2012, at 1:18 PM, Howard Jones wrote:
 
 HI Todd
 
 Script below. Your track range is 953-987 correct?
 
 Anyway I put your track into the tracker2Camera gizmo
 Created camera using 'create camera' under the 'Translate solves'
 
 That was it - worked fine, might even match your image. Use the latest 
 Tracker2Camera (attached again)
 
 The script below is set to HD as I dont know what format you are working in.
  
 Howard
 
 set cut_paste_input [stack 0]
 version 7.0 v1b38
 push $cut_paste_input
 Tracker3 {
  track1 {{curve x953 1192 1247.527466 1304.445923 1361.67395 1420.560303 
 1482.739014 1548.128296 1610.351685 1671.486572 1732.383667 1793.790527 
 1853.362915 1912.415894 1974.61438 2034.171753 2091.987915 2145.516113 
 2197.037842 2249.268921 2301.771729 2353.022583 2401.169312 2450.260254 
 2500.791992 2553.439941 2607.471924 2661.059082 2713.591431 2765.387695 
 2819.274414 2875.749146 2933.259277 2988.799438 3042.455322 3093.411133} 
 {curve x953 818 819.5675049 821.9576416 824.9746704 828.8840332 835.4890137 
 843.7455444 852.7792358 862.2110596 871.3128052 882.1752319 892.2661743 
 902.6511841 912.3652954 923.1884766 934.8099976 944.2409668 951.4041748 
 956.5293579 961.5074463 964.8376465 967.0097046 968.0718994 968.6292114 
 970.2266846 971.1508179 972.5056763 972.8568115 973.5623779 974.3269043 
 975.4362183 977.2075195 979.0283813 981.0758057 983.494873}}
  offset1 {0 0}
  pattern1 {-104 -54 104 54}
  search1 {-84 -77 84 77}
  track2 {1126 474}
  offset2 {0 0}
  pattern2 {-32 -32 32 32}
  search2 {-22 -22 22 22}
  track3 {1126 678}
  offset3 {0 0}
  pattern3 {-32 -32 32 32}
  search3 {-22 -22 22 22}
  track4 {922 678}
  offset4 {0 0}
  pattern4 {-32 -32 32 32}
  search4 {-22 -22 22 22}
  transform match-move
  reference_frame 953
  translate {{curve x953 0 55.52746582 112.4459229 169.6739502 228.5603027 
 290.7390137 356.1282959 418.3516846 479.4865723 540.383667 601.7905273 
 661.362915 720.4158936 782.6143799 842.1717529 899.987793 953.5161133 
 1005.037842 1057.269043 1109.771729 1161.022461 1209.169434 1258.260254 
 1308.791992 1361.439941 1415.471924 1469.059082 1521.591309 1573.387695 
 1627.274414 1683.749023 1741.259277 1796.799316 1850.455322 1901.411133} 
 {curve x953 0 1.567504883 3.957641602 6.97467041 10.8840332 17.48901367 
 25.74554443 34.77923584 44.21105957 53.31280518 64.17523193 74.26617432 
 84.65118408 94.36529541 105.1884766 116.8099976 126.2409668 133.4041748 
 138.5293579 143.5074463 146.8376465 149.0097046 150.0718994 150.6292114 
 152.2266846 153.1508179 154.5056763 154.8568115 155.5623779 156.3269043 
 157.4362183 159.2075195 161.0283813 163.0758057 165.494873}}
  center {{curve x953 1192 1192 1192 1192 1192 1192 1192 1192 1192 1192 1192 
 1192 1192 1192 1192 1192 1192 1192 1192 1192 1192 1192 1192 1192 1192 1192 
 1192 1192 1192 1192 1192 1192 1192 1192 1192} {curve x953 818 818 818 818 
 818 818 818 818 818 818 818 818 818 818 818 818 818 818 818 818 818 818 818 
 818 818 818 818 818 818 818 818 818 818 818 818}}
  name Tracker1
  selected true
  xpos -271
  ypos 130
 }
 CheckerBoard2 {
  inputs 0
  name CheckerBoard1
  selected true
  xpos -86
  ypos 131
 }
 Sphere {
  radius 0.01
  name Sphere1
  selected true
  xpos -86
  ypos 227
 }
 Camera2 {
  inputs 0
  translate {{-Tracker2Camera.solvedTranslate} 
 {-Tracker2Camera.solvedTranslate} {-Tracker2Camera.solvedTranslate}}
  focal {{Tracker2Camera.focalLengthCalc}}
  haperture {{Tracker2Camera.apertureCalc.x}}
  vaperture {{Tracker2Camera.apertureCalc.y}}
  name Camera1
  label translate
  selected true
  xpos -255
  ypos 247
 }
 Scene {
  inputs 2
  name Scene1
  selected true
  xpos -76
  ypos 290
 }
 tracker2Camera2 {
  inputs 0
  name Tracker2Camera
  note_font Arial
  selected true
  xpos -270
  ypos 179
  format 0
  apertureCalc {24.576 {apertureCalc.x*height/width}}
  fovCalc {{degrees(2*atan(apertureCalc/(2*focalLengthCalc)))} 
 {degrees(2*atan(apertureCalc/(2*focalLengthCalc)))}}
  apertureFocalRatio {{apertureCalc.x/focalLengthCalc.main}}
  Trax01 {{curve x953 1192 1247.527466 1304.445923 1361.67395 1420.560303 
 1482.739014 1548.128296 1610.351685 1671.486572 1732.383667 1793.790527 
 1853.362915 1912.415894 1974.61438 2034.171753 2091.987915 2145.516113 
 2197.037842 2249.268921 2301.771729 2353.022583 2401.169312 2450.260254 
 2500.791992 2553.439941 2607.471924 2661.059082 2713.591431 2765.387695 
 2819.274414 2875.749146 2933.259277 2988.799438 3042.455322 3093.411133} 
 {curve x953 818 819.5675049 821.9576416 824.9746704

Re: [Nuke-users] Can I use 2D track for 3D Camera?

2012-09-13 Thread Todd Groves 
I found it. I just have to scale it dramatically to match the size of the shots 
needs.




On Sep 13, 2012, at 2:51 PM, Todd Groves wrote:

 How do I scale the scene? The Camera moves in my 3D program, but only 
 slightly; which means I need to scale the scene before generating the FBX.
 
 
 
 On Sep 13, 2012, at 2:26 PM, Marten Blumen wrote:
 
 Not sure why it doesn't work, I can see the camera moving here
 
 On 14 September 2012 08:57, Todd Groves t...@nulightfx.com wrote:
 Hey Howard,
 
 The Axis moves, but the Camera doesn't move. Will that change if I use 
 WriteGeo to generate an FBX version?
 
 
 
 On Sep 13, 2012, at 1:18 PM, Howard Jones wrote:
 
 HI Todd
 
 Script below. Your track range is 953-987 correct?
 
 Anyway I put your track into the tracker2Camera gizmo
 Created camera using 'create camera' under the 'Translate solves'
 
 That was it - worked fine, might even match your image. Use the latest 
 Tracker2Camera (attached again)
 
 The script below is set to HD as I dont know what format you are working in.
  
 Howard
 
 set cut_paste_input [stack 0]
 version 7.0 v1b38
 push $cut_paste_input
 Tracker3 {
  track1 {{curve x953 1192 1247.527466 1304.445923 1361.67395 1420.560303 
 1482.739014 1548.128296 1610.351685 1671.486572 1732.383667 1793.790527 
 1853.362915 1912.415894 1974.61438 2034.171753 2091.987915 2145.516113 
 2197.037842 2249.268921 2301.771729 2353.022583 2401.169312 2450.260254 
 2500.791992 2553.439941 2607.471924 2661.059082 2713.591431 2765.387695 
 2819.274414 2875.749146 2933.259277 2988.799438 3042.455322 3093.411133} 
 {curve x953 818 819.5675049 821.9576416 824.9746704 828.8840332 835.4890137 
 843.7455444 852.7792358 862.2110596 871.3128052 882.1752319 892.2661743 
 902.6511841 912.3652954 923.1884766 934.8099976 944.2409668 951.4041748 
 956.5293579 961.5074463 964.8376465 967.0097046 968.0718994 968.6292114 
 970.2266846 971.1508179 972.5056763 972.8568115 973.5623779 974.3269043 
 975.4362183 977.2075195 979.0283813 981.0758057 983.494873}}
  offset1 {0 0}
  pattern1 {-104 -54 104 54}
  search1 {-84 -77 84 77}
  track2 {1126 474}
  offset2 {0 0}
  pattern2 {-32 -32 32 32}
  search2 {-22 -22 22 22}
  track3 {1126 678}
  offset3 {0 0}
  pattern3 {-32 -32 32 32}
  search3 {-22 -22 22 22}
  track4 {922 678}
  offset4 {0 0}
  pattern4 {-32 -32 32 32}
  search4 {-22 -22 22 22}
  transform match-move
  reference_frame 953
  translate {{curve x953 0 55.52746582 112.4459229 169.6739502 228.5603027 
 290.7390137 356.1282959 418.3516846 479.4865723 540.383667 601.7905273 
 661.362915 720.4158936 782.6143799 842.1717529 899.987793 953.5161133 
 1005.037842 1057.269043 1109.771729 1161.022461 1209.169434 1258.260254 
 1308.791992 1361.439941 1415.471924 1469.059082 1521.591309 1573.387695 
 1627.274414 1683.749023 1741.259277 1796.799316 1850.455322 1901.411133} 
 {curve x953 0 1.567504883 3.957641602 6.97467041 10.8840332 17.48901367 
 25.74554443 34.77923584 44.21105957 53.31280518 64.17523193 74.26617432 
 84.65118408 94.36529541 105.1884766 116.8099976 126.2409668 133.4041748 
 138.5293579 143.5074463 146.8376465 149.0097046 150.0718994 150.6292114 
 152.2266846 153.1508179 154.5056763 154.8568115 155.5623779 156.3269043 
 157.4362183 159.2075195 161.0283813 163.0758057 165.494873}}
  center {{curve x953 1192 1192 1192 1192 1192 1192 1192 1192 1192 1192 1192 
 1192 1192 1192 1192 1192 1192 1192 1192 1192 1192 1192 1192 1192 1192 1192 
 1192 1192 1192 1192 1192 1192 1192 1192 1192} {curve x953 818 818 818 818 
 818 818 818 818 818 818 818 818 818 818 818 818 818 818 818 818 818 818 818 
 818 818 818 818 818 818 818 818 818 818 818 818}}
  name Tracker1
  selected true
  xpos -271
  ypos 130
 }
 CheckerBoard2 {
  inputs 0
  name CheckerBoard1
  selected true
  xpos -86
  ypos 131
 }
 Sphere {
  radius 0.01
  name Sphere1
  selected true
  xpos -86
  ypos 227
 }
 Camera2 {
  inputs 0
  translate {{-Tracker2Camera.solvedTranslate} 
 {-Tracker2Camera.solvedTranslate} {-Tracker2Camera.solvedTranslate}}
  focal {{Tracker2Camera.focalLengthCalc}}
  haperture {{Tracker2Camera.apertureCalc.x}}
  vaperture {{Tracker2Camera.apertureCalc.y}}
  name Camera1
  label translate
  selected true
  xpos -255
  ypos 247
 }
 Scene {
  inputs 2
  name Scene1
  selected true
  xpos -76
  ypos 290
 }
 tracker2Camera2 {
  inputs 0
  name Tracker2Camera
  note_font Arial
  selected true
  xpos -270
  ypos 179
  format 0
  apertureCalc {24.576 {apertureCalc.x*height/width}}
  fovCalc {{degrees(2*atan(apertureCalc/(2*focalLengthCalc)))} 
 {degrees(2*atan(apertureCalc/(2*focalLengthCalc)))}}
  apertureFocalRatio {{apertureCalc.x/focalLengthCalc.main}}
  Trax01 {{curve x953 1192 1247.527466 1304.445923 1361.67395 1420.560303 
 1482.739014 1548.128296 1610.351685 1671.486572 1732.383667 1793.790527 
 1853.362915 1912.415894 1974.61438 2034.171753 2091.987915 2145.516113 
 2197.037842 2249.268921 2301.771729 2353.022583 2401.169312 2450.260254 
 2500.791992 2553.439941 2607.471924 2661.059082

Re: [Nuke-users] Can I use 2D track for 3D Camera?

2012-09-13 Thread Randy Little 
You have to make sure you units in Nuke and Modo are the same. and when you
import make sure the units are set correctly

Randy S. Little
http://www.rslittle.com http://reel.rslittle.com
http://www.imdb.com/name/nm2325729/





On Thu, Sep 13, 2012 at 2:59 PM, Todd Groves t...@nulightfx.com wrote:

 I found it. I just have to scale it dramatically to match the size of the
 shots needs.




 On Sep 13, 2012, at 2:51 PM, Todd Groves wrote:

 How do I scale the scene? The Camera moves in my 3D program, but only
 slightly; which means I need to scale the scene before generating the FBX.



 On Sep 13, 2012, at 2:26 PM, Marten Blumen wrote:

 Not sure why it doesn't work, I can see the camera moving here

 On 14 September 2012 08:57, Todd Groves t...@nulightfx.com wrote:

 Hey Howard,

 The Axis moves, but the Camera doesn't move. Will that change if I use
 WriteGeo to generate an FBX version?



 On Sep 13, 2012, at 1:18 PM, Howard Jones wrote:

 HI Todd

 Script below. Your track range is 953-987 correct?

 Anyway I put your track into the tracker2Camera gizmo
 Created camera using 'create camera' under the 'Translate solves'

 That was it - worked fine, might even match your image. Use the latest
 Tracker2Camera (attached again)

 The script below is set to HD as I dont know what format you are working
 in.

 Howard

 set cut_paste_input [stack 0]
 version 7.0 v1b38
 push $cut_paste_input
 Tracker3 {
  track1 {{curve x953 1192 1247.527466 1304.445923 1361.67395 1420.560303
 1482.739014 1548.128296 1610.351685 1671.486572 1732.383667 1793.790527
 1853.362915 1912.415894 1974.61438 2034.171753 2091.987915 2145.516113
 2197.037842 2249.268921 2301.771729 2353.022583 2401.169312 2450.260254
 2500.791992 2553.439941 2607.471924 2661.059082 2713.591431 2765.387695
 2819.274414 2875.749146 2933.259277 2988.799438 3042.455322 3093.411133}
 {curve x953 818 819.5675049 821.9576416 824.9746704 828.8840332 835.4890137
 843.7455444 852.7792358 862.2110596 871.3128052 882.1752319 892.2661743
 902.6511841 912.3652954 923.1884766 934.8099976 944.2409668 951.4041748
 956.5293579 961.5074463 964.8376465 967.0097046 968.0718994 968.6292114
 970.2266846 971.1508179 972.5056763 972.8568115 973.5623779 974.3269043
 975.4362183 977.2075195 979.0283813 981.0758057 983.494873}}
  offset1 {0 0}
  pattern1 {-104 -54 104 54}
  search1 {-84 -77 84 77}
  track2 {1126 474}
  offset2 {0 0}
  pattern2 {-32 -32 32 32}
  search2 {-22 -22 22 22}
  track3 {1126 678}
  offset3 {0 0}
  pattern3 {-32 -32 32 32}
  search3 {-22 -22 22 22}
  track4 {922 678}
  offset4 {0 0}
  pattern4 {-32 -32 32 32}
  search4 {-22 -22 22 22}
  transform match-move
  reference_frame 953
  translate {{curve x953 0 55.52746582 112.4459229 169.6739502 228.5603027
 290.7390137 356.1282959 418.3516846 479.4865723 540.383667 
 601.7905273661.362915 720.4158936 782.6143799 842.1717529 899.987793 
 953.5161133
 1005.037842 1057.269043 1109.771729 1161.022461 1209.169434 1258.260254
 1308.791992 1361.439941 1415.471924 1469.059082 1521.591309 1573.387695
 1627.274414 1683.749023 1741.259277 1796.799316 1850.455322 1901.411133}
 {curve x953 0 1.567504883 3.957641602 6.97467041 10.8840332 17.48901367
 25.74554443 34.77923584 44.21105957 53.31280518 64.17523193 74.26617432
 84.65118408 94.36529541 105.1884766 116.8099976 126.2409668 133.4041748
 138.5293579 143.5074463 146.8376465 149.0097046 150.0718994 150.6292114
 152.2266846 153.1508179 154.5056763 154.8568115 155.5623779 156.3269043
 157.4362183 159.2075195 161.0283813 163.0758057 165.494873}}
  center {{curve x953 1192 1192 1192 1192 1192 1192 1192 1192 1192 1192
 1192 1192 1192 1192 1192 1192 1192 1192 1192 1192 1192 1192 1192 1192 1192
 1192 1192 1192 1192 1192 1192 1192 1192 1192 1192} {curve x953 818 818 818
 818 818 818 818 818 818 818 818 818 818 818 818 818 818 818 818 818 818 818
 818 818 818 818 818 818 818 818 818 818 818 818 818}}
  name Tracker1
  selected true
  xpos -271
  ypos 130
 }
 CheckerBoard2 {
  inputs 0
  name CheckerBoard1
  selected true
  xpos -86
  ypos 131
 }
 Sphere {
  radius 0.01
  name Sphere1
  selected true
  xpos -86
  ypos 227
 }
 Camera2 {
  inputs 0
  translate {{-Tracker2Camera.solvedTranslate}
 {-Tracker2Camera.solvedTranslate} {-Tracker2Camera.solvedTranslate}}
  focal {{Tracker2Camera.focalLengthCalc}}
  haperture {{Tracker2Camera.apertureCalc.x}}
  vaperture {{Tracker2Camera.apertureCalc.y}}
  name Camera1
  label translate
  selected true
  xpos -255
  ypos 247
 }
 Scene {
  inputs 2
  name Scene1
  selected true
  xpos -76
  ypos 290
 }
 tracker2Camera2 {
  inputs 0
  name Tracker2Camera
  note_font Arial
  selected true
  xpos -270
  ypos 179
  format 0
  apertureCalc {24.576 {apertureCalc.x*height/width}}
  fovCalc {{degrees(2*atan(apertureCalc/(2*focalLengthCalc)))}
 {degrees(2*atan(apertureCalc/(2*focalLengthCalc)))}}
  apertureFocalRatio {{apertureCalc.x/focalLengthCalc.main}}
  Trax01 {{curve x953 1192 1247.527466 1304.445923 1361.67395 1420.560303
 1482.739014

Re: [Nuke-users] Can I use 2D track for 3D Camera?

2012-09-13 Thread Todd Groves 
Thanks, Randy. I got it working. :)



On Sep 13, 2012, at 3:11 PM, Randy Little wrote:

 You have to make sure you units in Nuke and Modo are the same. and when you 
 import make sure the units are set correctly
 
 Randy S. Little
 http://www.rslittle.com
 http://www.imdb.com/name/nm2325729/
 
 
 
 
 
 On Thu, Sep 13, 2012 at 2:59 PM, Todd Groves t...@nulightfx.com wrote:
 I found it. I just have to scale it dramatically to match the size of the 
 shots needs.
 
 
 
 
 On Sep 13, 2012, at 2:51 PM, Todd Groves wrote:
 
 How do I scale the scene? The Camera moves in my 3D program, but only 
 slightly; which means I need to scale the scene before generating the FBX.
 
 
 
 On Sep 13, 2012, at 2:26 PM, Marten Blumen wrote:
 
 Not sure why it doesn't work, I can see the camera moving here
 
 On 14 September 2012 08:57, Todd Groves t...@nulightfx.com wrote:
 Hey Howard,
 
 The Axis moves, but the Camera doesn't move. Will that change if I use 
 WriteGeo to generate an FBX version?
 
 
 
 On Sep 13, 2012, at 1:18 PM, Howard Jones wrote:
 
 HI Todd
 
 Script below. Your track range is 953-987 correct?
 
 Anyway I put your track into the tracker2Camera gizmo
 Created camera using 'create camera' under the 'Translate solves'
 
 That was it - worked fine, might even match your image. Use the latest 
 Tracker2Camera (attached again)
 
 The script below is set to HD as I dont know what format you are working 
 in.
  
 Howard
 
 set cut_paste_input [stack 0]
 version 7.0 v1b38
 push $cut_paste_input
 Tracker3 {
  track1 {{curve x953 1192 1247.527466 1304.445923 1361.67395 1420.560303 
 1482.739014 1548.128296 1610.351685 1671.486572 1732.383667 1793.790527 
 1853.362915 1912.415894 1974.61438 2034.171753 2091.987915 2145.516113 
 2197.037842 2249.268921 2301.771729 2353.022583 2401.169312 2450.260254 
 2500.791992 2553.439941 2607.471924 2661.059082 2713.591431 2765.387695 
 2819.274414 2875.749146 2933.259277 2988.799438 3042.455322 3093.411133} 
 {curve x953 818 819.5675049 821.9576416 824.9746704 828.8840332 
 835.4890137 843.7455444 852.7792358 862.2110596 871.3128052 882.1752319 
 892.2661743 902.6511841 912.3652954 923.1884766 934.8099976 944.2409668 
 951.4041748 956.5293579 961.5074463 964.8376465 967.0097046 968.0718994 
 968.6292114 970.2266846 971.1508179 972.5056763 972.8568115 973.5623779 
 974.3269043 975.4362183 977.2075195 979.0283813 981.0758057 983.494873}}
  offset1 {0 0}
  pattern1 {-104 -54 104 54}
  search1 {-84 -77 84 77}
  track2 {1126 474}
  offset2 {0 0}
  pattern2 {-32 -32 32 32}
  search2 {-22 -22 22 22}
  track3 {1126 678}
  offset3 {0 0}
  pattern3 {-32 -32 32 32}
  search3 {-22 -22 22 22}
  track4 {922 678}
  offset4 {0 0}
  pattern4 {-32 -32 32 32}
  search4 {-22 -22 22 22}
  transform match-move
  reference_frame 953
  translate {{curve x953 0 55.52746582 112.4459229 169.6739502 228.5603027 
 290.7390137 356.1282959 418.3516846 479.4865723 540.383667 601.7905273 
 661.362915 720.4158936 782.6143799 842.1717529 899.987793 953.5161133 
 1005.037842 1057.269043 1109.771729 1161.022461 1209.169434 1258.260254 
 1308.791992 1361.439941 1415.471924 1469.059082 1521.591309 1573.387695 
 1627.274414 1683.749023 1741.259277 1796.799316 1850.455322 1901.411133} 
 {curve x953 0 1.567504883 3.957641602 6.97467041 10.8840332 17.48901367 
 25.74554443 34.77923584 44.21105957 53.31280518 64.17523193 74.26617432 
 84.65118408 94.36529541 105.1884766 116.8099976 126.2409668 133.4041748 
 138.5293579 143.5074463 146.8376465 149.0097046 150.0718994 150.6292114 
 152.2266846 153.1508179 154.5056763 154.8568115 155.5623779 156.3269043 
 157.4362183 159.2075195 161.0283813 163.0758057 165.494873}}
  center {{curve x953 1192 1192 1192 1192 1192 1192 1192 1192 1192 1192 
 1192 1192 1192 1192 1192 1192 1192 1192 1192 1192 1192 1192 1192 1192 1192 
 1192 1192 1192 1192 1192 1192 1192 1192 1192 1192} {curve x953 818 818 818 
 818 818 818 818 818 818 818 818 818 818 818 818 818 818 818 818 818 818 
 818 818 818 818 818 818 818 818 818 818 818 818 818 818}}
  name Tracker1
  selected true
  xpos -271
  ypos 130
 }
 CheckerBoard2 {
  inputs 0
  name CheckerBoard1
  selected true
  xpos -86
  ypos 131
 }
 Sphere {
  radius 0.01
  name Sphere1
  selected true
  xpos -86
  ypos 227
 }
 Camera2 {
  inputs 0
  translate {{-Tracker2Camera.solvedTranslate} 
 {-Tracker2Camera.solvedTranslate} {-Tracker2Camera.solvedTranslate}}
  focal {{Tracker2Camera.focalLengthCalc}}
  haperture {{Tracker2Camera.apertureCalc.x}}
  vaperture {{Tracker2Camera.apertureCalc.y}}
  name Camera1
  label translate
  selected true
  xpos -255
  ypos 247
 }
 Scene {
  inputs 2
  name Scene1
  selected true
  xpos -76
  ypos 290
 }
 tracker2Camera2 {
  inputs 0
  name Tracker2Camera
  note_font Arial
  selected true
  xpos -270
  ypos 179
  format 0
  apertureCalc {24.576 {apertureCalc.x*height/width}}
  fovCalc {{degrees(2*atan(apertureCalc/(2*focalLengthCalc)))} 
 {degrees(2*atan(apertureCalc/(2*focalLengthCalc)))}}
  apertureFocalRatio

Re: [Nuke-users] Can I use 2D track for 3D Camera?

2012-09-13 Thread Howard Jones 
Out of interest did it work as Randy says. The tracker2camera is based on 1 
unit as far as I can tell. So did it work with a straight match of units? I 
know I wrote it but it's like bread - I don't have to know how to make it to 
drop toast butter side down. 

Haven't not used it for a long time I've just realised for a shot I'm doing 
with particles it will give me a quick way of tracking the emitting geo in. So 
been a useful relook at an old tool for me. 

I don't think I ever sussed out object scaling properly but I might look at 
that as well again. Though of course it'll never be a 3D tracker. 

Howard

On 13 Sep 2012, at 23:50, Todd Groves t...@nulightfx.com wrote:

 Thanks, Randy. I got it working. :)
 
 
 
 On Sep 13, 2012, at 3:11 PM, Randy Little wrote:
 
 You have to make sure you units in Nuke and Modo are the same. and when you 
 import make sure the units are set correctly
 
 Randy S. Little
 http://www.rslittle.com
 http://www.imdb.com/name/nm2325729/
 
 
 
 
 
 On Thu, Sep 13, 2012 at 2:59 PM, Todd Groves t...@nulightfx.com wrote:
 I found it. I just have to scale it dramatically to match the size of the 
 shots needs.
 
 
 
 
 On Sep 13, 2012, at 2:51 PM, Todd Groves wrote:
 
 How do I scale the scene? The Camera moves in my 3D program, but only 
 slightly; which means I need to scale the scene before generating the FBX.
 
 
 
 On Sep 13, 2012, at 2:26 PM, Marten Blumen wrote:
 
 Not sure why it doesn't work, I can see the camera moving here
 
 On 14 September 2012 08:57, Todd Groves t...@nulightfx.com wrote:
 Hey Howard,
 
 The Axis moves, but the Camera doesn't move. Will that change if I use 
 WriteGeo to generate an FBX version?
 
 
 
 On Sep 13, 2012, at 1:18 PM, Howard Jones wrote:
 
 HI Todd
 
 Script below. Your track range is 953-987 correct?
 
 Anyway I put your track into the tracker2Camera gizmo
 Created camera using 'create camera' under the 'Translate solves'
 
 That was it - worked fine, might even match your image. Use the latest 
 Tracker2Camera (attached again)
 
 The script below is set to HD as I dont know what format you are working 
 in.
  
 Howard
 
 set cut_paste_input [stack 0]
 version 7.0 v1b38
 push $cut_paste_input
 Tracker3 {
  track1 {{curve x953 1192 1247.527466 1304.445923 1361.67395 1420.560303 
 1482.739014 1548.128296 1610.351685 1671.486572 1732.383667 1793.790527 
 1853.362915 1912.415894 1974.61438 2034.171753 2091.987915 2145.516113 
 2197.037842 2249.268921 2301.771729 2353.022583 2401.169312 2450.260254 
 2500.791992 2553.439941 2607.471924 2661.059082 2713.591431 2765.387695 
 2819.274414 2875.749146 2933.259277 2988.799438 3042.455322 3093.411133} 
 {curve x953 818 819.5675049 821.9576416 824.9746704 828.8840332 
 835.4890137 843.7455444 852.7792358 862.2110596 871.3128052 882.1752319 
 892.2661743 902.6511841 912.3652954 923.1884766 934.8099976 944.2409668 
 951.4041748 956.5293579 961.5074463 964.8376465 967.0097046 968.0718994 
 968.6292114 970.2266846 971.1508179 972.5056763 972.8568115 973.5623779 
 974.3269043 975.4362183 977.2075195 979.0283813 981.0758057 983.494873}}
  offset1 {0 0}
  pattern1 {-104 -54 104 54}
  search1 {-84 -77 84 77}
  track2 {1126 474}
  offset2 {0 0}
  pattern2 {-32 -32 32 32}
  search2 {-22 -22 22 22}
  track3 {1126 678}
  offset3 {0 0}
  pattern3 {-32 -32 32 32}
  search3 {-22 -22 22 22}
  track4 {922 678}
  offset4 {0 0}
  pattern4 {-32 -32 32 32}
  search4 {-22 -22 22 22}
  transform match-move
  reference_frame 953
  translate {{curve x953 0 55.52746582 112.4459229 169.6739502 228.5603027 
 290.7390137 356.1282959 418.3516846 479.4865723 540.383667 601.7905273 
 661.362915 720.4158936 782.6143799 842.1717529 899.987793 953.5161133 
 1005.037842 1057.269043 1109.771729 1161.022461 1209.169434 1258.260254 
 1308.791992 1361.439941 1415.471924 1469.059082 1521.591309 1573.387695 
 1627.274414 1683.749023 1741.259277 1796.799316 1850.455322 1901.411133} 
 {curve x953 0 1.567504883 3.957641602 6.97467041 10.8840332 17.48901367 
 25.74554443 34.77923584 44.21105957 53.31280518 64.17523193 74.26617432 
 84.65118408 94.36529541 105.1884766 116.8099976 126.2409668 133.4041748 
 138.5293579 143.5074463 146.8376465 149.0097046 150.0718994 150.6292114 
 152.2266846 153.1508179 154.5056763 154.8568115 155.5623779 156.3269043 
 157.4362183 159.2075195 161.0283813 163.0758057 165.494873}}
  center {{curve x953 1192 1192 1192 1192 1192 1192 1192 1192 1192 1192 
 1192 1192 1192 1192 1192 1192 1192 1192 1192 1192 1192 1192 1192 1192 
 1192 1192 1192 1192 1192 1192 1192 1192 1192 1192 1192} {curve x953 818 
 818 818 818 818 818 818 818 818 818 818 818 818 818 818 818 818 818 818 
 818 818 818 818 818 818 818 818 818 818 818 818 818 818 818 818}}
  name Tracker1
  selected true
  xpos -271
  ypos 130
 }
 CheckerBoard2 {
  inputs 0
  name CheckerBoard1
  selected true
  xpos -86
  ypos 131
 }
 Sphere {
  radius 0.01
  name Sphere1
  selected true
  xpos -86
  ypos 227
 }
 Camera2 {
  inputs 0
  translate

Re: [Nuke-users] Can I use 2D track for 3D Camera?

2012-09-13 Thread Todd 
Basically I simply increased the scale until it looked right. I went by nothing in particular. I probably could look into more detail next time.  Thanks everyone for your help.Howard Jones  wrote:>Out of interest did it work as Randy says. The tracker2camera is based on 1 unit as far as I can tell. So did it work with a straight match of units? I know I wrote it but it's like bread - I don't have to know how to make it to drop toast butter side down.Haven't not used it for a long time I've just realised for a shot I'm doing with particles it will give me a quick way of tracking the emitting geo in. So been a useful relook at an old tool for me.I don't think I ever sussed out object scaling properly but I might look at that as well again. Though of course it'll never be a 3D tracker.HowardOn 13 Sep 2012, at 23:50, Todd Groves t...@nulightfx.com wrote:Thanks, Randy. I got it working. :)On Sep 13, 2012, at 3:11 PM, Randy Little wrote:You have to make sure you units in Nuke and Modo are the same. and when you import make sure the units are set correctlyRandy S. Littlehttp://www.rslittle.com
>
>http://www.imdb.com/name/nm2325729/
>On Thu, Sep 13, 2012 at 2:59 PM, Todd Groves t...@nulightfx.com wrote:
>
>I found it. I just have to scale it dramatically to match the size of the shots needs.On Sep 13, 2012, at 2:51 PM, Todd Groves wrote:
>
>How do I scale the scene? The Camera moves in my 3D program, but only slightly; which means I need to scale the scene before generating the FBX.
>
>On Sep 13, 2012, at 2:26 PM, Marten Blumen wrote:Not sure why it doesn't work, I can see the camera moving hereOn 14 September 2012 08:57, Todd Groves t...@nulightfx.com wrote:
>
>
>
>Hey Howard,The Axis moves, but the Camera doesn't move. Will that change if I use WriteGeo to generate an FBX version?
>
>
>
>On Sep 13, 2012, at 1:18 PM, Howard Jones wrote:
>
>
>
>HI ToddScript below. Your track range is 953-987 correct?Anyway I put your track into the tracker2Camera gizmoCreated camera using 'create camera' under the 'Translate solves'That was it - worked fine, might even match your image. Use the latest Tracker2Camera (attached again)
>
>
>
>The script below is set to HD as I dont know what format you are working in.Howard
>
>
>
>set cut_paste_input [stack 0]version
> 7.0 v1b38push $cut_paste_inputTracker3 {track1 {{curve x953 1192 1247.527466 1304.445923 1361.67395 1420.560303 1482.739014 1548.128296 1610.351685 1671.486572 1732.383667 1793.790527 1853.362915 1912.415894 1974.61438 2034.171753 2091.987915 2145.516113 2197.037842 2249.268921 2301.771729 2353.022583 2401.169312 2450.260254 2500.791992 2553.439941 2607.471924 2661.059082 2713.591431 2765.387695 2819.274414 2875.749146 2933.259277 2988.799438 3042.455322 3093.411133} {curve x953 818 819.5675049 821.9576416 824.9746704 828.8840332 835.4890137 843.7455444 852.7792358 862.2110596 871.3128052 882.1752319 892.2661743 902.6511841 912.3652954 923.1884766 934.8099976 944.2409668 951.4041748 956.5293579 961.5074463 964.8376465 967.0097046 968.0718994 968.6292114 970.2266846 971.1508179 972.5056763 972.8568115 973.5623779 974.3269043 975.4362183 977.2075195 979.0283813 981.0758057 983.494873}}
>
>
>
>offset1 {0 0}pattern1 {-104 -54
> 104 54}search1 {-84 -77 84 77}track2 {1126 474}offset2 {0 0}pattern2 {-32 -32 32 32}search2 {-22 -22 22 22}track3 {1126 678}offset3 {0 0}pattern3 {-32 -32 32 32}search3 {-22 -22 22 22}
>
>
>
>track4 {922 678}offset4 {0 0}pattern4 {-32 -32 32 32}search4 {-22 -22 22 22}transform match-movereference_frame 953translate {{curve x953 0 55.52746582 112.4459229 169.6739502 228.5603027 290.7390137 356.1282959 418.3516846 479.4865723 540.383667 601.7905273 661.362915 720.4158936 782.6143799 842.1717529 899.987793 953.5161133 1005.037842 1057.269043 1109.771729 1161.022461 1209.169434 1258.260254 1308.791992 1361.439941 1415.471924 1469.059082 1521.591309 1573.387695 1627.274414 1683.749023 1741.259277 1796.799316 1850.455322 1901.411133} {curve x953 0 1.567504883 3.957641602 6.97467041 10.8840332 17.48901367
> 25.74554443 34.77923584 44.21105957 53.31280518 64.17523193 74.26617432 84.65118408 94.36529541 105.1884766 116.8099976 126.2409668 133.4041748 138.5293579 143.5074463 146.8376465 149.0097046 150.0718994 150.6292114 152.2266846 153.1508179 154.5056763 154.8568115 155.5623779 156.3269043 157.4362183 159.2075195 161.0283813 163.0758057 165.494873}}
>
>
>
>center {{curve x953 1192 1192 1192 1192 1192 1192 1192 1192 1192 1192 1192 1192 1192 1192 1192 1192 1192 1192 1192 1192 1192 1192 1192 1192 1192 1192 1192 1192 1192 1192 1192 1192 1192 1192 1192} {curve x953 818 818 818 818 818 818 818 818 818 818 818 818 818 818 818 818 818 818 818 818 818 818 818 818 818 818 818 818 818 818 818 818 818 818 818}}
>
>
>
>name Tracker1selected truexpos -271ypos 130}CheckerBoard2 {inputs 0name CheckerBoard1selected truexpos -86ypos 131}Sphere {radius
> 0.01name Sphere1selected truexpos -86ypos 227}Camera2 {inputs 0translate

Re: [Nuke-users] Can I use 2D track for 3D Camera?

2012-09-12 Thread Marten Blumen 
Use the 'Add User Track' btn in Tracking tab in the CameraTracking node.

On 13 September 2012 08:13, Todd Groves t...@nulightfx.com wrote:

 In a shot I'm trying to get a Camera Track for, there is not enough
 parallax for the Cam Tracker to capture the dolly movement. Instead it
 interprets the camera movement as a pan.

 I believe if I can somehow use my 2D tracking information and apply it to
 the camera, I can use that inside my 3D app. Any suggestions?

 Thanks in advance.


 ___
 Nuke-users mailing list
 Nuke-users@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/
 http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users

___
Nuke-users mailing list
Nuke-users@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/
http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users

Re: [Nuke-users] Can I use 2D track for 3D Camera?

2012-09-12 Thread Todd Groves 
I did that, and pasted the 2D tracker data. But the camera does not move. 
Do I still track features?




On Sep 12, 2012, at 1:43 PM, Marten Blumen wrote:

 Use the 'Add User Track' btn in Tracking tab in the CameraTracking node.  
 
 On 13 September 2012 08:13, Todd Groves t...@nulightfx.com wrote:
 In a shot I'm trying to get a Camera Track for, there is not enough parallax 
 for the Cam Tracker to capture the dolly movement. Instead it interprets the 
 camera movement as a pan.
 
 I believe if I can somehow use my 2D tracking information and apply it to the 
 camera, I can use that inside my 3D app. Any suggestions?
 
 Thanks in advance.
 
 
 ___
 Nuke-users mailing list
 Nuke-users@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/
 http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users
 
 ___
 Nuke-users mailing list
 Nuke-users@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/
 http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users

___
Nuke-users mailing list
Nuke-users@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/
http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users

Re: [Nuke-users] Can I use 2D track for 3D Camera?

2012-09-12 Thread Howard Jones 
I think you mean convert it to use as a camera rather than for the camera 
tracker, do you? 
I wrote a tool to do that a few years which I thought I'd put on Nukepedia but 
must have dreamt it, so attached is a new version.
I only wrote it as a challenge and used it a couple of times in production so 
it's probably a bit ropey.

On creativeCrash at 
http://www.creativecrash.com/nuke/downloads/gizmos/3d/c/tracker2camera , but I 
think this version fails with multiviews which is fixed in attached.

Anyway copy your track into the node and then 'create scene' for static camera 
moving geo or 'create camera' for moving camera. Place geo at 0. I did try and 
set up one that allowed pushing back in z but cant remember correct maths 
unfortunatly.

Cheers 

Howard
p.s. this is the description from Creativecrash...


tracker2Camera is a quick and dirty 3D tracker. It takes a 
2Dtrack, and converts it to the equivalent 3D space and spits out a 
nodal camera/scene, or translating camera/axis depending on what you 
want to achieve. This way you can track a point and put in a 3D object. 
(For xy translate or nodal pans plus rotation only, for crazy moves 
you'll still need a 3D tracker.)





 From: Marten Blumen mar...@gmail.com
To: Nuke user discussion nuke-users@support.thefoundry.co.uk 
Sent: Wednesday, 12 September 2012, 21:43
Subject: Re: [Nuke-users] Can I use 2D track for 3D Camera?
 

Use the 'Add User Track' btn in Tracking tab in the CameraTracking node.  


On 13 September 2012 08:13, Todd Groves t...@nulightfx.com wrote:

In a shot I'm trying to get a Camera Track for, there is not enough parallax 
for the Cam Tracker to capture the dolly movement. Instead it interprets the 
camera movement as a pan.

I believe if I can somehow use my 2D tracking information and apply it to the 
camera, I can use that inside my 3D app. Any suggestions?

Thanks in advance.


___
Nuke-users mailing list
Nuke-users@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/
http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users


___
Nuke-users mailing list
Nuke-users@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/
http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users



tracker2Camera.gizmo
Description: Binary data
___
Nuke-users mailing list
Nuke-users@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/
http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users

Re: [Nuke-users] Can I use 2D track for 3D Camera?

2012-09-12 Thread Marten Blumen 
When you paste in the 2d track you then solve the camera. Its like
adding a really good tracking marker

On 9/13/12, Todd Groves t...@nulightfx.com wrote:
 I did that, and pasted the 2D tracker data. But the camera does not move.
 Do I still track features?




 On Sep 12, 2012, at 1:43 PM, Marten Blumen wrote:

 Use the 'Add User Track' btn in Tracking tab in the CameraTracking node.


 On 13 September 2012 08:13, Todd Groves t...@nulightfx.com wrote:
 In a shot I'm trying to get a Camera Track for, there is not enough
 parallax for the Cam Tracker to capture the dolly movement. Instead it
 interprets the camera movement as a pan.

 I believe if I can somehow use my 2D tracking information and apply it to
 the camera, I can use that inside my 3D app. Any suggestions?

 Thanks in advance.


 ___
 Nuke-users mailing list
 Nuke-users@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/
 http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users

 ___
 Nuke-users mailing list
 Nuke-users@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/
 http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users



-- 
Sent from my mobile device
___
Nuke-users mailing list
Nuke-users@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/
http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users

Re: [Nuke-users] Can I use 2D track for 3D Camera?

2012-09-12 Thread Howard Jones 

Use create camera instead - you should get a translating camera instead
 
Howard




 From: Todd Groves t...@nulightfx.com
To: Howard Jones mrhowardjo...@yahoo.com; Nuke user discussion 
nuke-users@support.thefoundry.co.uk 
Sent: Wednesday, 12 September 2012, 23:55
Subject: Re: [Nuke-users] Can I use 2D track for 3D Camera?
 

Hi Howard,


The Axis moves but the Camera is static. What am I missing?






On Sep 12, 2012, at 3:07 PM, Howard Jones wrote:

I think you mean convert it to use as a camera rather than for the camera 
tracker, do you? 
I wrote a tool to do that a few years which I thought I'd put on Nukepedia 
but must have dreamt it, so attached is a new version.
I only wrote it as a challenge and used it a couple of times in production so 
it's probably a bit ropey.

On creativeCrash at 
http://www.creativecrash.com/nuke/downloads/gizmos/3d/c/tracker2camera , but 
I think this version fails with multiviews which is fixed in attached.

Anyway copy your track into the node and then 'create scene' for static 
camera moving geo or 'create camera' for moving camera. Place geo at 0. I did 
try and set up one that allowed pushing back in z but cant remember correct 
maths unfortunatly.

Cheers 

Howard
p.s. this is the description from Creativecrash...



tracker2Camera is a quick and dirty 3D tracker. It takes a 
2Dtrack, and converts it to the equivalent 3D space and spits out a 
nodal camera/scene, or translating camera/axis depending on what you 
want to achieve. This way you can track a point and put in a 3D object. 
(For xy translate or nodal pans plus rotation only, for crazy moves 
you'll still need a 3D tracker.)






 From: Marten Blumen mar...@gmail.com
To: Nuke user discussion nuke-users@support.thefoundry.co.uk 
Sent: Wednesday, 12 September 2012, 21:43
Subject: Re: [Nuke-users] Can I use 2D track for 3D Camera?
 

Use the 'Add User Track' btn in Tracking tab in the CameraTracking node.  


On 13 September 2012 08:13, Todd Groves t...@nulightfx.com wrote:

In a shot I'm trying to get a Camera Track for, there is not enough parallax 
for the Cam Tracker to capture the dolly movement. Instead it interprets the 
camera movement as a pan.

I believe if I can somehow use my 2D tracking information and apply it to 
the camera, I can use that inside my 3D app. Any suggestions?

Thanks in advance.


___
Nuke-users mailing list
Nuke-users@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/
http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users


___
Nuke-users mailing list
Nuke-users@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/
http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users

tracker2Camera.gizmo___
Nuke-users mailing list
Nuke-users@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/
http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users


___
Nuke-users mailing list
Nuke-users@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/
http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users

Re: [Nuke-users] Can I use 2D track for 3D Camera?

2012-09-12 Thread Howard Jones 
I think there's a confusion going on. It sounds like the camera tracker can't 
solve because of lack of parallax. 

Adding a user track to this is unlikely to help assuming the cameratracker has 
tracked ok but not solved well. 

The gizmo takes 1 track and converts it into 3D space. Which is what you wanted 
to try. Whether it helps is a different issue of course. 

It spits out a rotating camera or translating camera solution. With the scene 
option giving you a static camera and moving geo. the translating camera option 
giving you moving camera static geo. Dont know why seemed like a good idea at 
the time and think was related to the original challenge set, which was to 
allow tracking a 3D object to a point. 

My gizmo is clearly not a camera tracker, it's far too simplistic for that. 

So track a point, put it into tracker2camera, and create translating camera, 
put your geo at 0 and it should them match that tracked point. Though not 
scale, that requires cleverer stuff. 

Lastly, although you have a rotation solution, and I assume you have checked 
you solved as free camera, is it close enough with a bit of fixing post scan 
line?

Howard

On 13 Sep 2012, at 00:25, Todd Groves t...@nulightfx.com wrote:

 I'm not sure I understand. I thought the gizmo was a replacement for the 
 CameraTracker.
 What's the workflow for this gizmo?
 
 
 
 On Sep 12, 2012, at 4:15 PM, Marten Blumen wrote:
 
 When you paste in the 2d track you then solve the camera. Its like
 adding a really good tracking marker
 
 On 9/13/12, Todd Groves t...@nulightfx.com wrote:
 I did that, and pasted the 2D tracker data. But the camera does not move.
 Do I still track features?
 
 
 
 
 On Sep 12, 2012, at 1:43 PM, Marten Blumen wrote:
 
 Use the 'Add User Track' btn in Tracking tab in the CameraTracking node.
 
 
 On 13 September 2012 08:13, Todd Groves t...@nulightfx.com wrote:
 In a shot I'm trying to get a Camera Track for, there is not enough
 parallax for the Cam Tracker to capture the dolly movement. Instead it
 interprets the camera movement as a pan.
 
 I believe if I can somehow use my 2D tracking information and apply it to
 the camera, I can use that inside my 3D app. Any suggestions?
 
 Thanks in advance.
 
 
 ___
 Nuke-users mailing list
 Nuke-users@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/
 http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users
 
 ___
 Nuke-users mailing list
 Nuke-users@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/
 http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users
 
 
 
 -- 
 Sent from my mobile device
 ___
 Nuke-users mailing list
 Nuke-users@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/
 http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users
 
 ___
 Nuke-users mailing list
 Nuke-users@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/
 http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users
___
Nuke-users mailing list
Nuke-users@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/
http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users

Re: [Nuke-users] Can I use 2D track for 3D Camera?

2012-09-12 Thread Todd Groves 
I thought by tracking a feature, I could paste that info into 2D track in the 
gizmo, then create camera to generate a moving camera. But, the camera 
doesn't move.
When I generate a scene and axis, the axis does move. Is there some way to 
attach the camera to the axis to make the camera move? Or am I missing a step 
here in creating 
a moving camera? Pressing create camera alone hasn't generated a moving 
camera.




On Sep 12, 2012, at 4:25 PM, Todd Groves wrote:

 I'm not sure I understand. I thought the gizmo was a replacement for the 
 CameraTracker.
 What's the workflow for this gizmo?
 
 
 
 On Sep 12, 2012, at 4:15 PM, Marten Blumen wrote:
 
 When you paste in the 2d track you then solve the camera. Its like
 adding a really good tracking marker
 
 On 9/13/12, Todd Groves t...@nulightfx.com wrote:
 I did that, and pasted the 2D tracker data. But the camera does not move.
 Do I still track features?
 
 
 
 
 On Sep 12, 2012, at 1:43 PM, Marten Blumen wrote:
 
 Use the 'Add User Track' btn in Tracking tab in the CameraTracking node.
 
 
 On 13 September 2012 08:13, Todd Groves t...@nulightfx.com wrote:
 In a shot I'm trying to get a Camera Track for, there is not enough
 parallax for the Cam Tracker to capture the dolly movement. Instead it
 interprets the camera movement as a pan.
 
 I believe if I can somehow use my 2D tracking information and apply it to
 the camera, I can use that inside my 3D app. Any suggestions?
 
 Thanks in advance.
 
 
 ___
 Nuke-users mailing list
 Nuke-users@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/
 http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users
 
 ___
 Nuke-users mailing list
 Nuke-users@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/
 http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users
 
 
 
 -- 
 Sent from my mobile device
 ___
 Nuke-users mailing list
 Nuke-users@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/
 http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users
 
 ___
 Nuke-users mailing list
 Nuke-users@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/
 http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users

___
Nuke-users mailing list
Nuke-users@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/
http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users