ollowing the recent clear nights I managed to grab 14hours on #IC1396#ElephantsTrunk#Redcat71#Atikone#EQ8#PixInsight#Astrophotography

ZWO FF80 ZWOASI533 400, 300 seconds exposures Stacked and edited in Pixinsight, tweaked in Photoshop

Following the recent clear nights I managed to grab 14hours on #IC1396#ElephantsTrunk#Redcat71#Atikone#EQ8#PixInsight#Astrophotography

and likewise, for our SYTN pix we typically tweak intensity levels (I use Lyn on the Mac) but none of that Siril and Pixinsight stuff that our amateur astronomy chums love doing

Cave Nebula, SH2-155, from last night. Really liking the new scope! 7hr30m x 360s Lights | Skywatcher Esprit 120 | iOptron CEM70 ZWO OAG + ASI178mm | Falcon Rotator V2 #Astronomy#Astrophotography#PixInsight

Immersed in a stellar sea, the Dumbbell Nebula (M27) glowed softly in the constellation Vulpecula last night. Total integration time of 3 hours. Processed in Pixinsight. #astrophotography

Unfortunately, there’s no direct method to pass weight maps between the two programs, combining them at different stages of your workflow—PixInsight for integration, APP for mosaic—should give you the best of both worlds.

Thanks, yes, that should indeed solve the problem! For this to work, though, the PixInsight exposure map would somehow need to be communicated to APP. Is that possible? Can I, say, get PixInsight to write out the weight map for each frame, and APP to read it for each frame?

After using PixInsight for custom-weighted integration, you can reimport the result into APP to continue your mosaic workflow. Using both tools together might resolve the uneven exposure without cropping. Let me know how it works for you!

If APP isn’t sufficient, PixInsight might help. It lets you create custom weights during integration, using a **Weighting Expression** for each pixel based on exposure and noise levels. This could provide a similar solution to what you're seeking.