-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Testing on Beta 39 - interface issues on App over AP #22
Comments
Thanks for the report! This morning I did finally figure out the bug where
the app when connected to the local AP do any detect the camera if the
camera was already connected when the app was opened. This fix will be in
the beta30 release tonight.
I don't know if the tracking/focus issues are related or not, but I'll try
to reproduce/fix any of them tonight to include in beta30.
Thanks!
Elijah
…On Sat, Jul 21, 2018 at 1:55 PM SteveLippitt ***@***.***> wrote:
Just been testing the app over the TL-VIEW access point. This new app
looks much nicer. I was interested in how it played with the Syrp Genie
Mini. Good news is that when bluetooth connects and Time-lapse+ VIEW 'sees'
the GM them I can control in camera menu. Also the inbuilt app in the VIEW
is working fine for the 15degree/hour pan.
Glitches that I notice are in the intervalometer menu under focus and
motion. Default for motion when GM is connected seems to be 'constant
rate', but if I select another method (e.g. 'Follow..') then I cannot find
anything on the interface that allows me to go back and change that
tracking choice.
To change the tracking choice I had to disconnect the camera and start
again.
I tested the motion control via the app on constant (putting 90
degrees/hour in to see what was going on) and it seems to be working fine.
Didn't try key frames, but would be happy to test when the interface has
been tested: let me know if that would help.
I think this part of the app interfaces needs a bit more testing before
you go for a GRC.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#22>, or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABNwThnKIwHiL6pgkv4T1dAmAysKzsldks5uI3k_gaJpZM4VZufv>
.
|
Thanks for the quick reply Elijah.
It must be a tough job trying to do all the development and testing on your
own. I’m happy to help out if you have any UAT scripts you want run and
reported on. I love the hardware and the app and can’t wait until you get
the app to a point where it is a rick solid v1.9 that I can stick with and
which I know exactly how to use and what it does.
Just let me know if I can help.
Best regards
Steve
On Sat, 21 Jul 2018 at 20:08, Elijah Parker <[email protected]>
wrote:
… Thanks for the report! This morning I did finally figure out the bug where
the app when connected to the local AP do any detect the camera if the
camera was already connected when the app was opened. This fix will be in
the beta30 release tonight.
I don't know if the tracking/focus issues are related or not, but I'll try
to reproduce/fix any of them tonight to include in beta30.
Thanks!
Elijah
On Sat, Jul 21, 2018 at 1:55 PM SteveLippitt ***@***.***>
wrote:
> Just been testing the app over the TL-VIEW access point. This new app
> looks much nicer. I was interested in how it played with the Syrp Genie
> Mini. Good news is that when bluetooth connects and Time-lapse+ VIEW
'sees'
> the GM them I can control in camera menu. Also the inbuilt app in the
VIEW
> is working fine for the 15degree/hour pan.
>
> Glitches that I notice are in the intervalometer menu under focus and
> motion. Default for motion when GM is connected seems to be 'constant
> rate', but if I select another method (e.g. 'Follow..') then I cannot
find
> anything on the interface that allows me to go back and change that
> tracking choice.
>
> To change the tracking choice I had to disconnect the camera and start
> again.
>
> I tested the motion control via the app on constant (putting 90
> degrees/hour in to see what was going on) and it seems to be working
fine.
> Didn't try key frames, but would be happy to test when the interface has
> been tested: let me know if that would help.
>
> I think this part of the app interfaces needs a bit more testing before
> you go for a GRC.
>
> —
> You are receiving this because you are subscribed to this thread.
> Reply to this email directly, view it on GitHub
> <#22>, or mute the thread
> <
https://github.com/notifications/unsubscribe-auth/ABNwThnKIwHiL6pgkv4T1dAmAysKzsldks5uI3k_gaJpZM4VZufv
>
> .
>
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#22 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AnmVWD3-uoUMghwS5w0T9jMV8WBjlrBdks5uI3w2gaJpZM4VZufv>
.
--
Steve Lippitt
Mobile: +44 7801 754 508
Home tel: +44 20 7602 2172
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Just been testing the app over the TL-VIEW access point. This new app looks much nicer - well done!
I was interested in how it played with the Syrp Genie Mini. The good news is that when bluetooth connects and Time-lapse+ VIEW 'sees' the GM, then I can control it fine using the camera menu in the app. Also, the in-built app in the VIEW is working fine for the 15degree/hour pan.
Glitches that I noticed are in the intervalometer menu under focus and motion. Default for motion when GM is connected seems to be 'constant rate', but if I select another method (e.g. 'Follow..') then I cannot find anything on the interface that allows me to go back and change that tracking choice.
To change the tracking choice I had to disconnect the camera and start again. It needs a button to allow users to change the tracking choice if they want to.
I tested the motion control via the app on constant (putting 90 degrees/hour in to see what was going on) and it seems to be working fine. Didn't try key frames, but would be happy to test when the interface has been tested: let me know if that would help. Key frames is my preferred use case so happy to help on testing.
I think this part of the app interfaces needs a bit more testing before you go for a GRC.
BTW - testing was with a Nikon D810
The text was updated successfully, but these errors were encountered: