15th Feb 2024: Astro Pixel Processor 2.0.0-beta29 released - macOS native File Chooser, macOS CMD-Q fixed, read-only Fits on network fixed and other bug fixes
7th December 2023: added payment option Alipay to purchase Astro Pixel Processor from China, Hong Kong, Macau, Taiwan, Korea, Japan and other countries where Alipay is used.
Mabula -
I tried all day to process my RGB and Ha data using the new multi channel workflow. But it keeps erroring out. Complaining about read-only permissions and not able to find some data temp files. See screenshots attached. I changed the APP folder to chmod 777 to no effect. I'm running on MacOS. I had same error on 1.060 before upgrading today. Help!
Error screen 1
Error screen 2
Maybe the @ sign in the filename ?
Hi Antoine @antoine,
Regarding the first screenshot:
the @ sign is probably the reason I think why it fails. On different file systems/OS's different characters are allowed in file names. And the @ character is defintely not allowed on all. Do other files without the @ sign load properly? The only fix here is to rename your files first using safe characters I think.
Regarding the second screen shot:
This could be same problem, what channel names did you use? Perhaps there is a character there is well that gives this problem. The channel name is used in the file-mapping in your harddrive so try to prevent characters that might not be allowed for now. I can fix this problem by catching the not-allowed characters off course.
Let me know if this explains the problem and if you can prevent it by using other characters in the filenames and channel names.
I probably need to figure out which characters are allowed and which not per Operating System to handle this properly.
Mabula
Mabula,
It all worked out when I used the standard "session" tags. Indeed the custom tags with the '@' or '/' characters created the issue. I should know that as a software engineer myself 🙂 Maybe you need to encode and properly escape those special characters in future versions? A small fix.
In any way, I am processing huge data and will report back soon. Thanks!
Thanks Mabula!
Processing works like a charm once I used the standard default session names. See the result below for a 2hr 37min integration over 3 nights and two cameras [QHY 367c and Nikon D810A]
Thank you @antoine for your feedback,
That sure looks great 😉
I will work to fix the problem that you reported off course.
Cheers,
Mabula
This just got me too - on Windows 10, a '/' in one of my groups was the problem. I'm still learning my way around APP, so my workaround was removing all of the subs in the group.
