Honestly, it doesn’t really matter what software you use as long as it can pipe out audio to a virtual cable or record the audio or baseband for use later (for APT be sure to resample recordings to 11,025 kHz with your software of choice - see below). For LRPT you may wish to use SDR# as the plugin and setup is well-supported, but it can be difficult to get set up right. Alternatives are available, such as the excellent SatDump suite (which does a lot more besides VHF and can also decode the NOAA VHF telemetry streams). It does not, sadly, do APT yet - but it is being added at some point soon. It can also work with RTL-SDR dongles for live decoding, which makes for an all-in-one solution when it’s all complete.

If you’re struggling for CPU clock cycles you can run with a low sample rate for this work. This is useful for RTL-SDR dongles. Both signals easily fit into a 250kbps sample rate. This also makes it doable on RPIs, but processing the data afterwards can take longer than other devices.

Here's the most cited/arguably the best setup guide for the LRPT SDR# path: https://happysat.nl/Setup_Meteor/Setup.html - If you're going with SatDump (which can now do live captures with some SDR hardware!) then just record your baseband and load it in. The user interface is quite simple (see below for more tips).

For APT there's lots out there already and it's just a simple virtual audio cable setup. If you’re struggling with stuttering audio then you’ll definitely have sync issues - the odd jump is fixable, sustained losses of data or gaps in the audio are not. There are resources available on how to adjust settings to try and fix this, but also your computer may just be not powerful enough.

Overriding pass auto-recording - you may need to tell WxtoImg to stop enabling recording when you’re trying to do other work in it. The best way to do this seems to be to deactivate the specific satellite the software is trying to record next from the list of satellites in the options - or untick them all. You may also need to do this to record one particular satellite if two passes are happening at the same time.

Composite tips - make sure that you make any changes to an image individually before saving the composite (that is, any of the options under the Image menu, such as equalising the image). Also images are saved in the order you add them to the composite - remember this when you’re after a certain image in a certain place. For example, two passes may cover the same area, but you want one shot over the other because it has better clouds.

Animations - it works, but it’s ropey, depending on the AVI format you choose. It may be better to transcode to MP4 afterwards if you want to do anything with it. Same tips here as for composites: make changes to each image individually! Another tip is to scale the timing/frames to match any big jumps, or you could try and do some interpolation? There’s lots of options. Captions would be good too, but you’ll need to edit your images or use a video editor app.

Desyncs/missing data - If you have a desync (such as jumps caused by interruptions in the audio - whether via a virtual cable or a real source) other software may be able to fix the WAV! NOAA-APT’s “Resample WAV” function under the Tools menu can process a WAV and then you can bring it into WxtoImg to do more work. It doesn’t always do it brilliantly, but small errors can be worked around.

Importing audio files tip - If you are bringing any audio file back into WxtoImg you will need to clone the timestamp from the original recording! If you don’t you may find your map overlays don’t work right. Again, NOAA-APT has a function for this in the Tools menu.

Recording passes for longer - If you improve your antenna’s low-angle gain make sure to adjust how early/late in a pass the recording runs. This can be found under Recording Options and is set by elevation angle on each side (useful if you’re blocked on one side - you can ignore it). Set a starting angle (bottom box) and a max elevation above which you want a recording to happen at all (top box).

Enhancements - NOAA-APT is a bit crap in this department, particular in how it handles the false colouring of images. See what you think - this is going to be a personal choice. If you find a good position for the sliders then well done!

Map overlays - this actually works well (and the adjustable-per-second correction can be very useful vs the fiddly WxtoImg “drag map overlay” option or messing about with timestamps). You will have to make completely transparent the lines you don't want to see, however, as you can't toggle things on and off.

If you don’t need map overlays for your LRPT captures then SatDump is a great solution that does everything you need and chucks out good images of a few different types. It’s certainly easier than setting up SDR# and multiple plugins and decoders and also opens up the world to further decoding of other satellites in other bands.

Do make sure you select the right sample rate (bandwidth selected in SDR application) and type when loading in your baseband. The box expects bits per second, rather than kilobits per second.

Symbol .S/.soft files have to have a specific filename or they won’t show up in the file open box, even if the extension matches. The format is that put out by the SDR# demodulator plug-in. If you want to load in a renamed file or a file from something else like SatDump you’ll need to type the first few characters and you’ll be able to click on the one you want. Annoying. That’s ham radio software, though!

Additionally, the ini files are what tell the software what mode you want to be in - you can drag the included ini files onto the exe file to start a particular one (after editing them to suit your needs) or you can rename one to the same name as the main ini file. The former option gives you more flexibility. You could even set up some .BAT files on your desktop to start in each mode. Perhaps in the future the developer will add the option to change modes within the software. You also have to quit and reload the app after each operation, it seems.

Honestly, don’t worry if you can’t figure this out. The software is absolutely horrible and very much part of the “someone made it work for them and then stopped caring” school of software development. As you’ll see from the pages online it has a specific list of requirements for things like folder and file names and the command line is unforgiving if you’re doing post-pass decoding. If you’re set on projections/composites/map overlays then it’s your only option, sadly.

(Put some useful commands here)