File extension not compatible with Nebulosity program

[Genoafire]

I used BYE  the other night and it worked perfectly, or so I thought. When it came time to stack and process the images in Nebulosity I was met with an error message saying that Nebulosity is unable to handle Light frame file names with an extension that contains parentheses.  It was interesting that it did not have a problem handling the dark frames which also contained  parentheses. How can I eliminate the parentheses, and if necessary the information contained within them,  appearing in the file extension for each light frame obtained in BYE?   Going through each file name on each light frame and renaming them is very time consuming. Thanks so much.

All the best,

Bob

[astroman133]

Please provide an example of a file name with parentheses in the extension. BYE should only create image files with .CR2, .CR3, .JPG, or .TIF extensions. Do you have periods in your filename template? If so, perhaps you could replace them with underscores.

That said, there is nothing illegal about a windows file extension that contains parentheses, so maybe Nebulosity has an issue.

[Genoafire]

I didn’t know I could set up my own file name template in BYE.  Please explain how I would do this. I do not see it addressed in the manual.   Thanks so much. 
Bob

[astroman133]

Open the Settings dialog and click on the ellipsis button beside the Filename template field to launch the Filename Template Editor. Customize the template as you wish. See my example below. Click Save when finished.

 

[Genoafire]

Here is a Screenshot. Hoping someone that has dealt with this before knows  exactly the procedure to just change a setting in BYE. It is apparently getting information from the Ascom setting for the mount  information. I don’t know if simply unchecking the box in the setting in the telescope screen on BYE would be the solution and not cause an error somewhere else?  

[Genoafire]

Thanks for the information Astroman. So this will override anything generated by BYE based upon the other settings?

[astroman133]

The issue is with the RA and DEC in the filename. They have periods in the values. I was correct that the file names are legal Windows names and the fact that Nebulosity cannot tolerate them is due to a problem with Nebulosity. You can remove those fields from your template to workaround the problem. You should also provide the example file name to Nebulosity so they can fix their app. The calibration frames probably do not have the RA and DEc fields in the name. That is why they are tolerated by Nebulosity.

 

[Genoafire]

The dark frames have the exact same information. Nebulosity processed those fine. I agree it is a problem with Nebulosity,  and the error message in nebulously actually stated the fact that it cannot handle parentheses.  As you said the solution is simply to change the file name template. Easy fix, Plus I can add the information that I want. I don’t really need The Ra Dec info. Thanks again for the solution and quick response. It has been time consuming to integrate the 10Micron GM1000 GPS software, BYE, ModelCreator, MGPbox, ASTAP, and Nebulosity into a working workflow. A lot of different manuals to read and unknown software interaction  But I am very close to “perfect” success . 🤗🤗

all the best,

Bob