So you don't want us to make this work in the new version? You just want to get an old version?
I had the issue in the webinar but I just tried to replicate it but could not.
Can you explain again what you are doing?
"makes my 1 to 0" - When does this happen? When you delete all numbers in the distance field? When a 0 is displayed and I type any digit, it switches to that digit.
here you a do it quick by
- type 50 mm of lens lensgth
- type 5 feets of distance
On rolled-out one, when hit 5 for the feets, it make 0. for me. latest firefox win7. rolled-over one might work better i remember. i make a cell phone movie to show if nomember can he vouche my bug.
you can tell my skill way less than normal guy and i dont know by guts feel, only know that 5 not 0 but not that 238.7 is maybe so not right on-site job, so frigntened to say obvious hurtful data.
i can and just will trust but if you thumb it up first
Tedor, this should be fixed now.
Instead of inserting a 0 when an entry is deleted, we just leave it blank. It's working a lot better for me. Try it out an let us know.
IPVMU Certified | 09/28/14 06:32am
Cleared browser cache and reloaded tool from new browser IE -11 session - still may have some issues when you change the Focal Length: (say from default 2mm to 20mm) and then change the Distancey: entry (usually by deleting the value in the field. When I change it sometimes displays an "Invalid Input!" value in the field. However, when I enter these values below they actually change on-the-fly as follows:
- type 5 it goes to 4
- type 6 it goes to 8
- type 3 it goes to 4.
However, once the first time sequence of numbers is entered, validated and displayed (i.e with the wrong value), the tool will then allow and accept whatever new value you enter on the next pass.
For what its worth, play with entering different combos in these fields and you'll see the varied results it returns - also was able to trigger the value displayed as "distance" in the same Distance: field.
Peter, Tedor, the distance input error is fixed.
Make sure to force refresh the page to make sure the new version gets loaded.
IPVMU Certified | 09/29/14 08:49pm
Great job everyone - I refreshed, reloaded (IE 11) and re-tested it again - and - it works!!
This great news, i confirm whatever you type stays typed!
But everybody is going to despict me for crashing parade too soon now:(((
The calculatator tells me 60mm lense is same good as 50mm lense, can that be by golly?
Pete W., does anything do anything anywhere differently on screen when you go from 50 to 60mm with the defaulter 1/3", 100ft dist, 1080P
Mine just stay 220.7 PPerF. I know, make video..
Small minor glitch, only not to mention.
Some times I get yellowish hard hat guy in picture, leaned in like a fixture, no matter what I try shake off, (except hit him back with hard reset, but lose all digit that I inputs to-date)
I made permalink evidences (cool!), now people will easier believe me.
If you get a bigger sensor, hopefully you get a bigger scenic view, this shall hold always true, unexceptedly?
When the other parmeter keep unchanged.
Ok. The thing works like a champ!
Now i know what may be little problem. I think that calcer is using wrong value for sensor size 1/1.27". Look like using 5.8 mm, should maybe 5.4?
to test screwy, start from scratch values, take account of width, should say 240 fts. Now change sensor to 1/2.7", it show 292.6, which could be true, cause sensor bigger so width get bigger. But then change to 1/2.5", width get smaller now, to 287.8. Something glitched up, or could this be right on? Maybe someone can have me verified too?
good news! I ask Svet, he say "probably one line of code, min". But you must remember, Svet is no programmer - and a bad one at that! So...
Have little prob using calculator:
When choosing Axis 4K P-1428e camera from list, it doesn't give me range for AOV, but the detailing page show varificle lens lengthen from 3.3 to 9.8 mm.
Also give ppf=0 for any feet away. Also finder not showing AOV on detailing page, just focalities.
Maybe im doing it wrong? (first time use model selector)
I like the upload scenes feature a lot! I hadn't gotten a chance to use it yet, and now that I have I'm stumped about one thing:
Basically, I choose the Q1755 from the list and set the AOV to 48, its widest. Then I upload a scene taken the with the same model camera, when at 48.
But even after I center it, I still have substantial top and bottom letterboxing. This letterboxing begins to shrink when increasing the focal length, but because it is several degrees before the letterboxing totally disappears, the cameras FOV at its widest is displayed until the FOV fills up the window. I would think that changing the AOV always changes the FOV, but in this case it just makes the FOV more magnified without reducing the width of the FOV.
When uploading a scene taken at a certain AOV and then using a camera with the same AOV, should the scene fill the window perfectly?
Should I just adjust the AOV of the new scene to whatever it takes up the whole window?
Side note: 29MP resolution is not available in manual mode. You can, howover choose the Avigilon behemoth from the list and then go into manual mode and change the sensor to 35mm. Which I works I think...
F-stop calculator always makes Lens B win, it's not fair!