Error saving TIFF
 
Share:
Notifications
Clear all

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.

 

Error saving TIFF

7 Posts
2 Users
1 Likes
1,685 Views
(@tschuh)
White Dwarf
Joined: 5 years ago
Posts: 13
Topic starter  

I'm getting this Java error in recent days with either 1.082 or 1.083-beta1.  It doesn't seem to matter what settings I use for the TIFF.  8-bit, 16-bit, 32-bit float, different ICC pallets.  All the same.  Any input welcome.

image

 


   
ReplyQuote
Topic Tags
(@tschuh)
White Dwarf
Joined: 5 years ago
Posts: 13
Topic starter  

Ok, I'm getting the same sort of error with JPEG as well.

image

   
ReplyQuote
(@wvreeven)
Quasar
Joined: 6 years ago
Posts: 2133
 

@tschuh Do you get the error as well when saving to FITS? Is your working folder on the internal hard drive or an external one? If external, what type is it? Normal HD or SSD?


   
ReplyQuote
(@tschuh)
White Dwarf
Joined: 5 years ago
Posts: 13
Topic starter  

@wvreeven  No problem saving FITS files.  Internal SSD storage.  I've been using this PC with APP for over a year now.

This post was modified 3 years ago by tschuh

   
ReplyQuote
(@wvreeven)
Quasar
Joined: 6 years ago
Posts: 2133
 

@tschuh So you probably get this error after processing a FITS file in APP, correct? Can you explain exactly what steps you do to get to this error and upload the FITS file that was used to

https://upload.astropixelprocessor.com/

using upload1 as both username and password? Please create a folder called tschuh_tiff_error and put the FITS file in there. Then we will have a look.


   
ReplyQuote
(@tschuh)
White Dwarf
Joined: 5 years ago
Posts: 13
Topic starter  

@wvreeven  I was about to upload my FITS when I figured out what the problem was.  My A/V software (Avast) was *silently* blocking not the fwrite() but the APP application itself.  A recent update made that block more vocal and it was highlighted as a blocked application, false positive for ransomware of all things.  I've whitelisted the app and all appears to be working correctly again.


   
ReplyQuote
(@wvreeven)
Quasar
Joined: 6 years ago
Posts: 2133
 

@tschuh Good to read that you found the cause!


   
ReplyQuote
Share: