Light Frames Won't Load

[Ojiisan]

I've been using Pixinsight for about a year now and love the program. I've not had any trouble with it until now. Two nights ago I captured 65 light frames of Comet V2 Johnson with BackYard Nikon. Pixinsight will not load these files into Batch PreProcessing. It loads darks, flats, bias, and light frames from other sessions that night but not these. Thinking it might be a drive problem I moved all the files onto another drive. Pixinsight will now add them, but I get an error message. Has anyone else had a similar problem or a suggestion as to what may be the hang up? Is it more likely a BYN issue? I've attached a jpg of the error message. Thanks.

https://www.flickr.com/photos/hawaiibirds/albums/72157631586761431

[msmythers]

The spaces in the folder names could be the problem.


Mike

[Ojiisan]

Thanks for your reply. That was it!!!   How weird

[msmythers]

Some file systems won't allow a null in a file(folder) name. Since PI works with other file systems I think the reason is to maintain cross-platform conformity.


Mike

[Ojiisan]

I can't thank you enough. I was about to pull out what little hair I have left.

[Niall Saunders]

Ojiisan,

Don't worry - all the best astroimagers are bald

[pfile]

ordinarily i think PI handles spaces in paths ok. this is on OSX, right? one problem could be that ":" used to be the file hierarchy delimiter in mac OS 9 and earlier, and so apple still wants to parse that as though it were a "/". i've seen this problem in other applications. generally speaking unix filename rules are different than windows and "legacy" macos, so spaces and other 'weird' characters need to be escaped. i am just wondering if it's the combination of spaces and ":" that messed things up here.

rob

[jshortt]

I would bet that the colon in the folder name (C: etc) is the problem

John