Jump to content

Canada's top-tier Telescopes & Accessories
Be as specific as possible when reporting issues and *ALWAYS* include the full version number of the application you are using and your exact *CAMERA MODEL*
NEVER POST YOUR KEY IN ANY PUBLIC FORUM, INCLUDING THE O'TELESCOPE SUPPORT FORUM ::: IF YOU DO YOUR KEY WILL BE DEACTIVATED WITHOUT NOTICE!
  • 0

Filename duration, extra zeroes


UNMANNED
 Share

Question

I'm having a problem with duration in my filenames - there are three '0' added; for instance when I take a 30sec exposure, in the filename it writes it as 30000sec. Any way to fix this?

Camera: Nikon D5500
Software version: 2.1.1
Win10 Pro

Link to comment
Share on other sites

  • Answers 8
  • Created
  • Last Reply

Top Posters For This Question

8 answers to this question

Recommended Posts

  • 0

Finally got to this.  You have Windows set to English, but somehow you have your decimal represented by a comma instead of a period.... and when BYE cast bulb duration into a number it assumes that you choose 90,000 seconds instead of 90.000 seconds. 

Link to comment
Share on other sites

  • 0

BYE and BYN are build from the same code base and if a problem like yours occurs with one product it usually happens with the other. However, I could not duplicate your issue with BYE 3.2.2 and my Canon T5i.

In the Filename Template Editor, my Name item 3 is specified as "<duration>s_". It appears in the file names as :

LIGHT_30s_1600iso_+22c_20210514-09h45m55s335ms.CR2 for a BULB exposure

and as

LIGHT_Tv30s_1600iso_+22c_20210514-09h47m32s295ms.CR21600iso_+22c_20210514-09h47m32s295ms.CR2 for a Tv exposure.

I would suggest upgrading to the latest release of BYN. Also please let us know if this fixes your issue. If it doesn't, it could be important to know if the exposure is a BULB exposure or a Tv (Timed value) exposure. Also it would be worth reviewing your filename template for how the <duration> item and surrounding text is specified.

 

Link to comment
Share on other sites

  • 0

Hey, thank you for your reply

I updated to ver. 2.1.2 which is the latest version and the problem still exists.
I'm using bulb exposure, and I screenshoted the settings (in the attachment), could any of the settings be causing it?

Also last two screenshots are capture settings and the resulting filename


 

1.png

2.png

3.png

4.png

5.png

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Answer this question...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

 Share


×
×
  • Create New...

Important Information

This site uses cookies to offer your a better browsing experience. You can adjust your cookie settings. By closing this banner, scrolling this page, clicking a link or continuing to browse otherwise, you agree to the use of cookies, our Privacy Policy, and our Terms of Use