johnpd About point 3, we have a few more questions want to ask you.
Could you tell us usually what you NEED to do with .TIFF files after sharpening? and what file format are you want for post-process after videostack? TIFF or fits?

Thanks.

@Tech@ZWO#58292 thanks for clarifying! Would it be an option to remove it from the Mac AppStore then? Just to clean up and prevent us users from being confused. Thanks again!

Olli

    @Tech@ZWO#58294
    I have uploaded the Saturn .AVI file here:
    https://drive.google.com/file/d/1YZ4MY5N_mr3Texs5iHHtqQuOF1qb3RjP/view?usp=sharing

    I have also copied the associated .TXT file here:
    https://drive.google.com/file/d/1xcpi7h2bBIU9jetIbiOMfpvFCupnAY8Y/view?usp=sharing

    Regarding not be able to drag and drop images, that now works. Apparently there is an issue with using it right after installation.

    Regarding having .TIFF output images, I might want to do additional processing with the output including using software such as Topaz GigaPixel to blow it up a little. If you gave a .FITS option, that would also be ok as I can easily convert that.

    JohnD

      ASIStudio 1.6.3 on Linux (Kubuntu 22.04)
      Hi. First of all, Thank You for porting ASIStudio to Linux.
      I downloaded and installed ASIStudio 1.6.3 on Kubuntu 22.04. The applications (ASILive, ASICap, ASIImg) launch and are able to connect to the cameras, however they do not detect or connect to the EAF (focuser) or EFW. The EFW and EAF selection boxes appear blank. Both the EFW and EAF are connected to the computer. KStars/EKOS (installed on the same computer) detects and connects to all of the devices just fine, so I don't think it's a connectivity issue.


      Thanks,
      Peter

        johnpd There will be a beta version of ASIStudio v1.7, you can try that soon.

        johnpd
        Hi John,
        ASIVideoStack will automatically save the fit file in a new file, you can find it where your .avi is.

        enigmaticastro
        Hi Peter,
        Conveyed this issue to the team, and we are trying to reproduce it, will get back to you once we get any progress.

        @ASIStudio@ZWO#58433

        OK I have the .FITS file, but it is very over exposed and virtually impossible to work with. I will have to see what the new version does.

        JohnD

          johnpd try canceling the "auto" button in the histogram and click the "reset' button, you will see a normal image.

          @ASIStudio@ZWO#58442

          OK, so instead of being able to adjust the output directly from ASIVideoStack. it requires you to open the .FITS output of ASIVideoStack in ASIFitsView and then at least adjust the over-stretch there. Kind of a roundabout way of doing it. However any sharpness or noise reduction cannot be applied to the .FITS file as that is written out as soon as the video is stacked, only to a saved .JPG file in ASIVideoStack and ASIFitsView has no sharpness or noise adjustment options.

          JohnD

            enigmaticastro
            Hi We tested, but didn't reproduce the problem, could you send the log for analysis?

            Thanks.

            @Tech@ZWO#58472
            You fixed it! Just kidding, but it is somehow working now.
            I could not get it to recognize the EFW and EAF all weekend. Perhaps I had not power cycled the entire rig (mount, EAF, EFW, cameras) after initial installation (although I know I rebooted the computer). Looking forward to trying out EAA from the Linux platform attached to the scope.

            Thanks,
            Peter

            7 days later

            johnpd Hi John,
            The FitsView is adjusted for deep sky images, so currently when you preview planetary images with auto stretch, it will over-expose, and we will note this issue and improve it.
            You can toggle off auto and reset the histogram to view the planetary images.

            @ASIStudio@ZWO#58684
            Thanks. That needs to be fixed as the resulting saved image is garbage unless the adjusted image can be save.

            JohnD

              johnpd
              Noted.
              The fit file is normal, so the fit file can be used. The problem lies in the preview, although the preview is over-exposed, it does not hurt the fit file.

              Here is the Jupiter video you took, we stacked it to get a fit, then add it to the FitsViewer.

              Write a Reply...