Manually set fps sample rate prior to capture?

[bXi0YAX]

I don't have tracking yet for my 12" dob so I have to let planets drift across the fov. That said, my capture window is limited and I can probably get two captures of about 200 frames each (@ 20fps & 5x zoom) before having to move the scope for another two. In doing so, have to account for the sample rate test at the beginning of each capture, which cuts into my limited time window.

Is there a way to set the fps sample rate manually?

[astroman133]

No, the LiveView frame rate is not controllable.

[bXi0YAX]

3 hours ago, astroman133 said:

No, the LiveView frame rate is not controllable.

So there is no way to bypass the annoying test that is ran prior to each and every LiveView capture? It seems redundant to run it every time and, like I said, it cuts into precious capture time. It'd be better to run it once and have it apply to the entirety of the session (from camera connect/disconnect).

[astroman133]

I don't disagree. You should create a post in the Suggestion Box Forum to allow the LiveView frame rate test to be bypassed per a new setting. Be sure to state your reasons why such a change would benefit your workflow.

The frame rate is not that useful to experienced users, but it may be used internally to determine the most efficient way to process the incoming data.

You can use the Loop count to direct BYE to capture multiple AVI files. This only causes the frame rate to be sampled once. You can also  loop numerous times and  for example you can use a capture to reposition the scope and then throw that capture away.

[bXi0YAX]

Alright, thanks for the help. I'm fairly new to BYE so wasn't sure if I was missing something or not.

[astroman133]

When your latest post came in I was editing my previous post. Please re-read.

[bXi0YAX]

9 minutes ago, astroman133 said:

You can use the Loop count to direct BYE to capture multiple AVI files. This only causes the frame rate to be sampled once. You can also  loop numerous times and  for example you can use a capture to reposition the scope and then throw that capture away.

Ah, this might be a viable solution. Although, It seems a bit "hackish" trying to workaround the issue.

[astroman133]

I would say that it is only an issue if the program is not behaving as the developers designed it to. Obviously the frame rate sampling is by design. It just doesn't seem to work with your equipment. Some could say trying to image with a scope that doesn't track is itself a bit hackish. I am not trying to be mean or offensive, but that was my first thought when I read your original post.

[bXi0YAX]

No, you're right. Its a good solution until I can get some form of tracking (I'm actually designing an eq platform at the moment), and even then I'm probably still going to use the looping feature. Thanks again for the help