The iPad also froze and need to be restarted. When I connected the camera to the qdslr app the AHG was not available. The solution-I hope- is to go to settings>general> auto lock> never…) I just determined this in my last, 3rd attempt. (The reason the camera froze is because the iPad went to sleep. I have learned from past attempts with dslrd that I cannot connect my camera to the emotimo without first connecting to dslrd, this is true for the new version of qdd.Įverything seemed to be working perfectly ( I was so excited-what a great software app!)Ībout 10 mins into the time-lapse my camera froze (blue spinning circle in the viewfinder) The only way to un-freeze is to remove the battery and restart the camera. I have tried 3 times to use qdsl and have failed for various reasons.Ĭonnected qDD and started auto holy Grail. ![]() Here are some of the issues I have come across. So PLEASE swap short and long pressing of the network button in the next Softwarerelease to get a quick connection to the APs default IP 192.168.1.1.Īnd I hope I can finally get all the bugs out of qdslr and get it to work. This can be used to connect over internet.Ĭall me a fool but who the f**k needs a multicast search on an Australian public-multicast IP 224.1.2.3 if there is absolutely nothing to find while the camera is connected through a local AP on 192.168.1.1 (by default!!!) at 99% of all users!? Long press – will display a dialog where you can enter the IP address of the machine running DslrDashboardServer (ddserver) or qDslrDashboard. The network communication is using 4757 TCP port. Search is done with multicast messages over 224.1.2.3:4757 (UDP). Single press – will initiate a search over your local network for DSLR cameras connected to DslrDashboardServer (ddserver) running on an OpenWrt router (like the TP-Link MR3040) or DSLR cameras connected to qDslrDashboard running on another PC or Android device. I made an update to the newest DDserver with the same problem).ĭon’t know if there are configuration items for the wireless connection… do you have any idea? Therefore, the reason must be either my connections (thru a TPLink) or the algorithm used in qdsldashboard. in helicon (on Android 4.4 connected to my d800 thru usb), the refocus works perfect (when switching from point ‘1’ to ‘2’) (helicon also works with 2 definied focus points). ![]() in qdslrdaschboard (connected to my D800 thru a TPLink), the refocus is not exact when siwtching from point ‘1’ to ‘2’ (it does not refocus exactly to the definied point) same result on ipad AIR 2 and Android 4.4 I tested the focus-switching between the 2 defined focus points: With Helicon, the focus stacking works with ALL my lenses exactly as desired. ![]() Meanwhile, I tested helicon (wired thru usb) – just to find a way thru my problem. That’s exactly the workflow I followed (with the results as described: no exact refocus when starting the focus stacking etc.).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |