I would be ever so grateful if the wonderful developers might consider exploring some delightful resources on Universal design principles! It seems, with all due respect to their amazing talents, that the interface may have accidentally evolved in a direction that presents charming little puzzles for users like myself!
For instance:
The software appears to take a little rest when encountering Ser files - how adorable!
The logs offer such mysterious little riddles instead of specific guidance - like a sweet game of charades where Iām left guessing what might have upset the program! It pauses so thoroughly afterward, perhaps enjoying a little meditation break?
Even after Iāve gone through the absolutely delightful adventure of using PIPP to separate my Ser file into individual fits, lovingly stacked them, and attempted to create an RGB, Iām blessed with another adorable mystery message saying itās ānot okā - such a creative way to maintain suspense!
This interface design is such a unique approach compared to Universal design principles! If these brilliant developers were students in my UX class, Iād simply have to give them a special creative award for thinking so far outside the conventional box of user-friendliness!
The poster would do well to report issues in a more constructive manner, because to the developers (probably volunteers working in their spare time) this will read as an insult. Instead of walking into the forum guns blazing, perhaps consider including actual messages, logs, etc.
I would be absolutely thrilled, my good person, to share the most adorable logs with everyone, IF they contained even the tiniest hint of helpful information! Thatās precisely the sweet little point I was trying to make with my heartfelt honestlyblunt, but Ill received message: the error notifications are so delightfully minimalist that they leave everything to the imagination! The logs are refreshingly concise and mysteriously poetic in their communication style! Itās like receiving a beautiful blank greeting card - so much potential, yet leaving me to fill in all the meaningful details myself!
But perhaps if someone can provide insight and derive what exactly is wrong with this, considering ever other piece of software out there loads the files without complaint, I would be eternally grateful.
File Z:\astronomy\2025-05-25\M57 (NGC 6720,Ring Nebula)\02_25_20_Green.ser was not recognised as readable by Siril, skipping
21:47:32: Skipping input file Z:\astronomy\2025-05-25\M57 (NGC 6720,Ring Nebula)\02_25_20_Green.ser (failed to be opened)
siril at this point is locked up and utterly refuses to do any other process until its restarted.
If you canāt communicate like a fully formed adult, then you donāt need to be here. Please do better, or find somewhere that will tolerate your style of communication.
Imagine coming into a new community seeking assistance and these are your first two message, how embarassing.
What a delightfully creative way to report a, issue! Iām absolutely charmed by your poetic approach to technical communication - itās like receiving feedback written by someone who thinks condescension is a programming language.
Now, regarding your adorable SER file issue: The error message youāve finally shared actually contains useful information, unlike your initial theatrical performance. The file 02_25_20_Green.ser isnāt being recognized, which typically indicates either file corruption or an unsupported SER variant.
Since you mentioned other software handles these files fine, could you share which capture software created this SER file? Different applications sometimes use slightly different SER implementations, and knowing the source helps us improve compatibility.
Hereās a revolutionary idea: instead of putting on this charming theatrical show, sending a sample of the problematic SER file would be infinitely more intelligent. Weāre developers, not fortune tellers - we canāt debug files we canāt examine.
I do appreciate that you eventually provided actual technical details. Perhaps in future, leading with actionable information rather than the creative writing exercise might yield faster results? Just a thought from someone who apparently needs that āspecial creative awardā you mentioned.
Thank you for your response! The files were lovingly and painstakingly created using SharpCap.
Iād be happy to share a sample file for troubleshooting. Where would be best to send these? They are quite substantial in size however In my continued testing, Iāve discovered something interesting! SIRIL processes these files perfectly when they reside locally on my drive, but encounters errors when accessing them over the NAS. This suggests SIRIL might be implementing some form of file locking thatās incompatible with iSCSI connections.
Copying everything to a local drive would be a solution if it werenāt impractical due to the sheer volume of astronomical data weāre processing. Perhaps in future development, considering network storage compatibility might be helpful suggestion? Looking forward to your thoughts on resolving this NAS access issue!
In any case some attention needs to be paid to how these things fail, because that log may be meaningful to you as a developer, as a user without intimate knowledge of the underlying code, means very little to me. same with when aligning the images in composting and the terse message of ānot goodā. There is nothing actionable in that the user can do. why is it ānot goodā at a minimum is a valid thing to display.
Donald Norman wrote an excellent book on the subject called āThe design of everyday thingsā. it goes into quite some depth on what makes a thing intuitive and easy to use, and is considered the authority on the subject.
