Filenames contain TvBulb instead of duration

[rpungello]

I have BYN set to use exposure duration in my filenames, but it seems like BYN will randomly use TvBulb instead of the actual duration, leaving me with files that don't sort properly because most of them are "120s" and the rest are "TvBulbs" (I'm leaving out the other parts of the filenames).

 

Is there something I can do about this?

[tcab]

Any progress on this bug?

I just did a short capture session and look how many occurrences of _TvBulbs_ happened in my file names.  I have now to figure out and repair seven files out of twenty - thats a 35% file name corruption rate - time that I'd rather spend processing my photos!

[admin]

Looking at it, it's a work in progress.

[admin]

Actually I made a small change last week, please download 2.0.5 from the pre-release download section.  Keep my posted on your findings please.

https://www.otelescope.com/files/category/24-pre-releases/

[admin]

Please let me know if you try the pre-release and it works (or not) I'd like to have this fix be the next release.

Regards,

[admin]

I would really like it is someone having this issue could test the pre-release to see if this was fixed with the change I made.

https://www.otelescope.com/files/category/24-pre-releases/

 

 

[tcab]

Initial testing with a D7200 indicates that the "Bulb" wording seems to have been fixed and that phrase no longer appears.

The "Tv" text appears in filenames which have non bulb shutter settings - not sure if this is intentional?

[tcab]

P.S. Here is another capture session mainly using non bulb settings.  Perhaps Tv means non bulb mode and that the number, if it has more than one digit, is to be interpreted as a fraction?

Although of course you can generate 2 second files in two ways e.g. _Tv2s_ and _2s_ which are both 2 seconds, the latter being bulb shutter.

Here is the result of such a a session (see image for session plan).

16:48 TEST205AGAIN_LIGHT_Tv2s_1600iso_4-0_20170607-16h48m05s833ms.NEF
16:48 TEST205AGAIN_LIGHT_Tv2s_1600iso_4-0_20170607-16h47m58s636ms.NEF
16:47 TEST205AGAIN_LIGHT_Tv2s_1600iso_4-0_20170607-16h47m51s732ms.NEF
16:47 TEST205AGAIN_LIGHT_Tv2s_1600iso_4-0_20170607-16h47m44s811ms.NEF
16:47 TEST205AGAIN_LIGHT_Tv1s_1600iso_4-0_20170607-16h47m38s141ms.NEF
16:47 TEST205AGAIN_LIGHT_Tv1s_1600iso_4-0_20170607-16h47m31s937ms.NEF
16:47 TEST205AGAIN_LIGHT_Tv1s_1600iso_4-0_20170607-16h47m25s891ms.NEF
16:47 TEST205AGAIN_LIGHT_Tv1s_1600iso_4-0_20170607-16h47m19s666ms.NEF
16:46 TEST205AGAIN_LIGHT_Tv12s_1600iso_4-0_20170607-16h46m53s057ms.NEF
16:46 TEST205AGAIN_LIGHT_Tv12s_1600iso_4-0_20170607-16h46m47s226ms.NEF
16:46 TEST205AGAIN_LIGHT_Tv12s_1600iso_4-0_20170607-16h46m41s978ms.NEF
16:46 TEST205AGAIN_LIGHT_Tv12s_1600iso_4-0_20170607-16h46m36s284ms.NEF
16:47 TEST205AGAIN_LIGHT_Tv110s_1600iso_4-0_20170607-16h47m14s327ms.NEF
16:47 TEST205AGAIN_LIGHT_Tv110s_1600iso_4-0_20170607-16h47m08s950ms.NEF
16:47 TEST205AGAIN_LIGHT_Tv110s_1600iso_4-0_20170607-16h47m04s040ms.NEF
16:47 TEST205AGAIN_LIGHT_Tv110s_1600iso_4-0_20170607-16h46m58s797ms.NEF
16:48 TEST205AGAIN_LIGHT_2s_1600iso_4-0_20170607-16h48m36s054ms.NEF
16:48 TEST205AGAIN_LIGHT_2s_1600iso_4-0_20170607-16h48m28s810ms.NEF
16:48 TEST205AGAIN_LIGHT_2s_1600iso_4-0_20170607-16h48m20s926ms.NEF
16:48 TEST205AGAIN_LIGHT_2s_1600iso_4-0_20170607-16h48m13s782ms.NEF

 

[s3igell]

5 hours ago, tcab said:

The "Tv" text appears in filenames which have non bulb shutter settings - not sure if this is intentional?

"Tv" is a long-held term used throughout Photography for "Shutter Priority" (or "Shutter Control") - meaning Exposures where the Shutter Speed is Dictated and any other related Parameters are hence Processor-calculated. Similarly, "Av" means "Aperture Priority".  (Why not use "Sv"??  Who knows, but "s" was already used for "Seconds".)

[admin]

Also called Timed Value.

[admin]

Oh, and when a non-bulb value is used the number displayed is used in the filename with Tv###s but the illegal file characters are removed so this is why 1/2 seconds shows as Tv12s.

Regards,

[tcab]

I'm also getting this weird naming - has there been a fix yet?  I'm getting:

• _30s_   (what I expect)
• _Tv30s_
• _TvBulbs_

Thus if there is a pattern, it seems that the duration in seconds is being replaced with "TvBulb" or the duration is being prepended with "Tv".

[astroman133]

What is in your filename template (Settings dialog) for exposure duration?

What version of BYN are you using? If you are not on 2.0.4 then you should upgrade and try to reproduce your issue. I would expect that it is not yet fixed since Guylain is good about posting here about the resolution of an issue.

[admin]

No fix yet, it is bit difficult to fix because I can't reproduce... but this is a bug for sure as it's been reported a few times by a few people.

In your case, do you get this only when images are 30 seconds?

[tcab]

I reproduced the problem on my first attempt, on a new D7200 camera, and after installing the latest 2.0.4 premium edition, using the following plan - see attached image.  The files created are also listed in the attached image.  During this session a weirdly named file was created for each duration, 4s, 30s and 60s.  Thus I think we can generalise that the weird naming kicks in at any duration.

I hope this helps towards tracking down this annoying problem. Its tiresome to have to go and repair file names constantly, and trying to figure out (by the date/time of the file) what duration it should actually be, and often having to preview files to guess their exposure etc.  I vote that this is a fairly high priority bug.

 

[admin]

Send me the log files, I've never seen this before so I'm curious to see what the log files will say.

Regards,

[rpungello]

I attached a zip file with the 3 log files from around the right time

Logs.zip

[admin]

Thanks for the log files.  There are no errors in them to help me find the root cause.  

This is a bug for sure and I will need to time to try and reproduce it.

Thanks for reporting it.

[rpungello]

Let me know if you need anything else from me. As a fellow software dev I understand how hard unreproducible bugs can be to track down.

[ceararizona]

The same happened to me, any solution?

 

[admin]

Yep, a bug which has not been fixed yet.

Regards,

 

[jcbeyer]

I'm seeing the same thing with my trial version.   I'm imaging with a D800E and D7200.  The latter seemed to generate more of this type of file.  In addition, the program recognized and connected both cameras quickly and triggered images for about an hour then abruptly froze or disconnected.  I had to close down Windows to clear the hung BYNikon screen as it was totally unresponsive to anything I tried. 

[admin]

21 minutes ago, jcbeyer said:

I'm seeing the same thing with my trial version.   I'm imaging with a D800E and D7200.  The latter seemed to generate more of this type of file.  In addition, the program recognized and connected both cameras quickly and triggered images for about an hour then abruptly froze or disconnected.  I had to close down Windows to clear the hung BYNikon screen as it was totally unresponsive to anything I tried. 

 

Camera disconnect it almost always a cable/usb connection issue.  

Are you using a hub?

How long is your usb cable?

[astroman133]

The disconnects should probably go on a new thread in order to avoid confusion.

[jcbeyer]

My apologies I will start a separate thread to address the disconnect problem.  My purpose for introducing it here was to make an association between the two observations.  Thank for the recommendation.